Triage

Move issues on the project issue tracker through a small state machine of triage roles.

Every comment or issue posted to the issue tracker during triage must start with this disclaimer:

> *This was generated by AI during triage.*

Reference docs

Agent Briefs

An agent brief is a structured comment posted to an issue that gives an AFK agent everything it needs to implement the fix or feature without human hand-holding. A good agent brief contains:

• Context: why this issue matters, relevant background, links to related issues or ADRs
• Scope: exactly what needs to change — no more, no less
• Acceptance criteria: a checklist of verifiable conditions that define "done"
• Relevant files: key files or modules to read first (not an exhaustive list — just the entry points)
• Constraints: things the agent must NOT do (e.g., don't refactor unrelated code, don't change the public API)

Keep briefs tight. An agent brief is not a tutorial — it is a specification. Assume the agent can read code; don't transcribe the codebase into the brief.

Out-of-Scope Knowledge Base

The .out-of-scope/ directory is a knowledge base of rejected features. Each file is a short markdown document explaining why a particular enhancement was declined. The pattern:

• When closing a wontfix enhancement, write a file to .out-of-scope/<slug>.md documenting the request and the rationale for rejection.
• Link to that file from the issue closing comment so future reporters can find the reasoning.
• When triaging a new issue, read .out-of-scope/*.md and surface any prior rejection that resembles the current issue — this prevents re-litigating decided questions.

Each .out-of-scope/ file should contain: a one-line summary of the feature request, the date it was declined, the rationale (technical, product, or strategic), and links to the original issue(s).

Roles

Two category roles:

• bug — something is broken
• enhancement — new feature or improvement

Five state roles:

• needs-triage — maintainer needs to evaluate
• needs-info — waiting on reporter for more information
• ready-for-agent — fully specified, ready for an AFK agent
• ready-for-human — needs human implementation
• wontfix — will not be actioned

Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.

These are canonical role names — the actual label strings used in the issue tracker may differ. Check the project's AGENTS.md or existing issue labels to find the mapping.

State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, or wontfix. needs-info returns to needs-triage once the reporter replies. The maintainer can override at any time — flag transitions that look unusual and ask before proceeding.

Invocation

The maintainer invokes /triage and describes what they want in natural language. Interpret the request and act. Examples:

• "Show me anything that needs my attention"
• "Let's look at #42"
• "Move #42 to ready-for-agent"
• "What's ready for agents to pick up?"

Show what needs attention

Query the issue tracker and present three buckets, oldest first:

1. Unlabeled — never triaged.
2. needs-triage — evaluation in progress.
3. needs-info with reporter activity since the last triage notes — needs re-evaluation.

Show counts and a one-line summary per issue. Let the maintainer pick.

Triage a specific issue

1. Gather context. Read the full issue (body, comments, labels, reporter, dates). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Read .out-of-scope/*.md and surface any prior rejection that resembles this issue.

2. Recommend. Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the issue. Wait for direction.

3. Reproduce (bugs only). Before any grilling, attempt reproduction: read the reporter's steps, trace the relevant code, run tests or commands. Report what happened — successful repro with code path, failed repro, or insufficient detail (a strong needs-info signal). A confirmed repro makes a much stronger agent brief.

4. Grill (if needed). If the issue needs fleshing out, use a grilling skill if available: invoke /grill-me if it is installed, or ask probing questions directly if no grilling skill is available.

5. Apply the outcome:

   • ready-for-agent — post an agent brief comment (see Agent Briefs section above).
   • ready-for-human — same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).
   • needs-info — post triage notes (template below).
   • wontfix (bug) — polite explanation, then close.
   • wontfix (enhancement) — write to .out-of-scope/, link to it from a comment, then close (see Out-of-Scope Knowledge Base section above).
   • needs-triage — apply the role. Optional comment if there's partial progress.

Quick state override

If the maintainer says "move #42 to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (role changes, comment, close), then act. Skip grilling. If moving to ready-for-agent without a grilling session, ask whether they want to write an agent brief.

Needs-info template

## Triage Notes

**What we've established so far:**

- point 1
- point 2

**What we still need from you (@reporter):**

- question 1
- question 2

Capture everything resolved during grilling under "established so far" so the work isn't lost. Questions must be specific and actionable, not "please provide more info".

Resuming a previous session

If prior triage notes exist on the issue, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.