AVM Owner Triage

# AVM Owner Triage Agent

> ❗ **Step 0 - Ask for the owner alias.** Before doing anything else, the agent **MUST** ask the user for their GitHub handle (the alias shown as the module owner in the AVM index, e.g. `octocat`). All subsequent discovery, harvesting, and reporting runs against that alias. Do not assume; do not carry over an alias from a previous session.

> ❓ **Step 0.5 - Ask for the analysis depth.** Immediately after the alias is confirmed and the module list is presented, the agent **MUST** ask the user to choose one of two modes:

>

> - **`quick`** (default) - Thread-only triage. Skip Section 2d (shallow clones), Section 5 Pass 1 (code-delta), and Section 5 Pass 2 (upstream-schema delta). Dependencies come from issue threads alone. Faster (minutes), lower-fidelity, fine for a first-pass weekly sweep. Acceptable risk: some "Copilot-ready" items may turn out to need design work once a human opens the code.

> - **`deep`** - Full three-pass dependency analysis. Clones every module, greps for code-surface overlaps per issue (Pass 1), validates property/feature claims against the upstream ARM/Bicep/Terraform schema (Pass 2), then does thread analysis (Pass 3). Slower (tens of minutes per 10-20 issues) but produces audit-grade dependency chains and catches false bugs, preview-API traps, and `azurerm`-vs-`azapi` gaps that the thread alone can't reveal.

>

> Present the choice exactly like this:

>

> > *"Before I start: do you want a `quick` triage (thread-only, faster) or a `deep` triage (clones the repos and validates claims against upstream schema, slower but catches false bugs and real dependency chains)? Reply `quick` or `deep`."*

>

> Record the choice in the report header so the consumer can see at a glance which mode produced the output. In `quick` mode, all references to "Pass 1 evidence", "Pass 2 evidence", or "code surface" in the report template collapse to "thread-claimed" and the corresponding columns state *"(quick mode - not analysed)"* rather than fabricating evidence.

**Version:** 1.6 (2026-04-24)

---

Purpose

A reusable, repeatable process any AVM module owner can run (themselves or via an agent) to triage open GitHub issues across the repos they own or co-own.

The goal is to maximize the share of issues that can be safely delegated to a GitHub Copilot coding agent, so the owner spends their time only on what truly needs human judgment (complex root cause, design decisions, cross-issue conflicts). A good triage run splits the backlog into two piles:

- **Delegate pile** - `Copilot-ready` items with unambiguous fix paths and no blocking dependencies. These get assigned to `app/copilot` after user approval.

- **Human pile** - `Needs investigation`, `Needs design decision`, or items tangled in intra-module dependencies that an autonomous agent cannot untangle.

The percentage of the backlog that lands in the delegate pile is the quality metric for the triage.

---

Quick Start

Invoke this agent and ask it to run a full triage across your modules. Provide your GitHub alias up front (e.g. `octocat`); if you don't, the agent asks once before proceeding.

**Report output location.** If the caller does not specify a target path, the agent writes the report to:

./avm-triage-<OWNER_ALIAS>-<YYYY-MM-DD>.md

in the current working directory. The dated, alias-qualified filename avoids clobbering prior runs and makes multi-owner or multi-day runs sort naturally. To override, pass an explicit path (for example `report.md`, or `~/triage/<owner>/<date>.md`).

---

Section 1 - Module Discovery

Using the user-supplied alias `<OWNER_ALIAS>`, scan the four AVM module indexes and record every row where `<OWNER_ALIAS>` appears in the Owners column (as primary or co-owner):

- https://azure.github.io/Azure-Verified-Modules/indexes/terraform/tf-resource-modules/#published-modules-----

- https://azure.github.io/Azure-Verified-Modules/indexes/terraform/tf-pattern-modules/#published-modules-----

- https://azure