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.*

On a local-markdown tracker, comments are written into a committed .md file, so hard-wrap every comment and triage note to ≤100 characters per line (prose only — leave tables and fenced code blocks intact) to satisfy markdownlint MD013. See issue-tracker-local.md.

Reference docs

• AGENT-BRIEF.md — how to write durable agent briefs
• OUT-OF-SCOPE.md — how the .out-of-scope/ knowledge base works

Roles

Two category roles:

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

Six 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
• tracking — container/parent issue (e.g. a PRD) that has been broken into sub-issues; the real work lives in the children
• 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. The mapping should have been provided to you - run /setup-zsl-superpowers if not.

State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, tracking, or wontfix. needs-info returns to needs-triage once the reporter replies. tracking is set automatically by /to-issues after it breaks an issue into sub-issues, and the parent auto-closes when the last child closes (no manual transition needed). 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.

   Guard against a pull-request reference (GitHub trackers only). Resolve the reference per docs/agents/issue-tracker.md for this repo's tracker — don't assume GitHub. Only when the configured tracker is GitHub: a bare number can resolve to a PR (issues and PRs share one number space), so if the fetched object's URL contains /pull/, confirm the user meant that reference before proceeding. Local-markdown and GitLab trackers don't have this collision.

   PRD tag check. If the issue is a PRD (has a ## User Stories section) OR is a child of one (resolve the parent via ## Parent link or sub-issue relationship), validate the parent PRD's user-story tags before moving the issue to ready-for-agent:

   • Every story must have at least one AC<n>: acceptance-criterion sub-bullet.
   • Any story carrying no AC<n>: criterion is invalid. A legacy observable: sub-bullet (pre-AC-split PRDs) counts as one acceptance criterion for back-compat; a legacy acceptance: tag, if present, is ignored.

   On failure, refuse to advance to ready-for-agent and tell the maintainer which stories are missing a criterion. Recommended fix: edit the PRD directly to add the missing AC<n>: criteria per /to-prd's story format. For legacy PRDs (written before acceptance criteria were required), the maintainer can re-run /to-prd on the existing conversation or hand-edit. needs-info, ready-for-human, wontfix, and tracking transitions are still allowed on criterion-less PRDs — only the agent-handoff path requires criteria, because /tdd-parallel will refuse on them.

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 — post an agent brief comment (AGENT-BRIEF.md).
   • 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).
   • tracking — the issue has open sub-issues; the work lives in the children. Apply the role and stop. Triage each child individually.
   • wontfix (bug) — polite explanation, then close.
   • wontfix (enhancement) — write to .out-of-scope/, link to it from a comment, then close (OUT-OF-SCOPE.md).
   • needs-triage — apply the role. Optional comment if there's partial progress.

6. Sync the project board (if configured). If docs/agents/project-board.md exists, after the label change above, also update the issue's project item Status:

   1. Read the project node ID, Status field ID, and the canonical-state → option-ID mapping from docs/agents/project-board.md.
   2. Resolve the GitHub issue number N. With a GitHub tracker it's the issue you're triaging. With a hybrid tracker (docs/agents/issue-tracker.md is the local-markdown-plus-mirror variant), the unit of work is a .scratch/ file — read its github: frontmatter to get the mirror issue number N; if the file has no github: value it was never mirrored, so log "no GitHub mirror; skipping Status update" and continue. Then look up the project item:

      gh api graphql -f query='query { repository(owner:"<owner>", name:"<repo>") { issue(number:N) { projectItems(first:20) { nodes { id project { id } } } } } }'

      Filter by project.id matching the configured project node ID. If no match, log "issue not in configured project; skipping Status update" and continue.
   3. Map the new state label to its Status option ID via the mapping table.
   4. Update via:

      gh api graphql -f query='mutation($p:ID!,$i:ID!,$f:ID!,$o:String!){updateProjectV2ItemFieldValue(input:{projectId:$p,itemId:$i,fieldId:$f,value:{singleSelectOptionId:$o}}){projectV2Item{id}}}' \
        -f p=<project-node-id> -f i=<item-id> -f f=<status-field-id> -f o=<option-id>

   5. Mention the Status change in the same triage summary you print to the maintainer.

   The label transition is the source of truth; the board sync is best-effort. If the Status update fails, surface the error but do not roll back the label change.

   Skip this step entirely if docs/agents/project-board.md doesn't exist.

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.