groundwork:triage

Move issues on the configured issue tracker through a small state machine of triage roles. This is the inbound front door: real bug reports and feature requests land here before a PRD or a tracer-bullet slice ever gets written for them.

0. Preconditions

Read docs/groundwork/config.json. If it doesn't exist, don't stop - bootstrap it per the "Lazy bootstrap" section of the groundwork setup skill: detect tracker and project type, write the config with defaults, state the assumptions in one line, and continue. Running setup explicitly is only for customizing.

This skill assumes an external tracker with real issues, labels, comments, and reporters (tracker: "github" or "linear"). If config.json's tracker is "local", tell the user triage doesn't apply - local mode has no inbound-issue concept to sort, only docs/groundwork/features/NNNN-slug/tasks.md entries that to-issues already created with a type and status - and stop.

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

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 agent to build directly (no PRD/slice needed)
• 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. Only the five state roles are configurable: their label strings come from docs/groundwork/config.json's triage_role_labels field (not triage_labels, which is a separate, unrelated list to-issues applies to every issue it creates). If a state role is missing from triage_role_labels (or the field is empty), that role's label string equals its own name; tell the user to run setup to override any of them. The two category roles (bug, enhancement) are fixed - always use those exact strings, no config override exists for them.

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 docs/groundwork/glossary.md, respecting any accepted ADRs in the area (docs/groundwork/adr/ for system-wide decisions, or the relevant feature's docs/groundwork/features/NNNN-slug/adr/ if the issue clearly belongs to work already in flight). 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 interview, 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. Interview (if needed). If the issue needs fleshing out, use the groundwork:interview-loop technique - ask detailed, one-at-a-time questions until every branch of the issue is resolved.
5. Apply the outcome:
   • ready-for-agent - post an agent brief comment (AGENT-BRIEF.md). Give it **Type:** AFK in the brief so build can pick it up directly, exactly like a to-issues-created slice.
   • ready-for-human - same structure as an agent brief, but **Type:** HITL, and 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 (OUT-OF-SCOPE.md).
   • 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 the interview - but never skip the Agent Brief: ready-for-agent/ready-for-human are only reachable with one posted (see the outcome rules above), since build depends on its Type field to treat the issue as workable. Draft it from the issue's existing content; if something the template needs (acceptance criteria, current/desired behavior) is genuinely missing, ask the maintainer that one thing rather than reopening a full interview session.

Needs-info template

> *This was generated by AI during triage.*

## 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 the interview 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.

Relationship to to-issues

to-issues slices a prd.md into tracer-bullet work; triage sorts issues that already exist and, for ready-for-agent/ready-for-human outcomes, makes them directly buildable without a PRD at all. If an issue turns out to need real design work during the interview, tell the maintainer it's grown past a quick triage and suggest survey or to-prd instead of forcing an agent brief onto something underspecified.