triage

name	triage
description	Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Triage

Move local markdown issues through a small state machine of triage roles.

Every triage note appended to a local issue file must start with this disclaimer:

> *This was generated by AI during triage.*

Reference docs

• AGENT-BRIEF.md — how to write durable agent briefs
• OUT-OF-SCOPE.md — how the .out-of-scope/ knowledge base works
• ../setup-skills/issue-tracker.md — local markdown tracker layout
• ../setup-skills/triage-labels.md — Category: and Status: metadata values
• ../setup-skills/domain.md — domain doc lookup rules

The setup docs above should be present. Run /setup-skills if they are missing or stale.

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. In the local tracker, these are stored as Category: and Status: fields near the top of the issue file. If state roles conflict, flag it and ask the maintainer before doing anything else.

These are canonical role names. The markdown field values are defined in ../setup-skills/triage-labels.md.

State transitions: an issue without Status: 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 .scratch/local-tracker/issues/01-localize-triage.md"
• "Move .scratch/local-tracker/issues/01-localize-triage.md to ready-for-agent"
• "What's ready for agents to pick up?"

Show what needs attention

Scan .scratch/**/issues/*.md and present three buckets, oldest first:

1. Missing metadata — no Status: field yet.
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 file (body, comments, Category:, Status:, reporter/date fields if present). 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, run a /grill-with-docs session.

5. Apply the outcome:

   • ready-for-agent — set Status: ready-for-agent and append an agent brief under ## Comments (AGENT-BRIEF.md).
   • ready-for-human — set Status: ready-for-human and append the same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).
   • needs-info — set Status: needs-info and append triage notes under ## Comments (template below).
   • wontfix (bug) — set Status: wontfix and append a polite explanation under ## Comments.
   • wontfix (enhancement) — write to .out-of-scope/, link to it from a comment in the issue file, then set Status: wontfix (OUT-OF-SCOPE.md).
   • needs-triage — set Status: needs-triage. Optional comment if there's partial progress.

Quick state override

If the maintainer says "move .scratch/local-tracker/issues/01-localize-triage.md to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (metadata changes and any appended comment), 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.