triagelisted

# 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-BRIEF.md](AGENT-BRIEF.md) — how to write durable agent briefs - [OUT-OF-SCOPE.md](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 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. The mapping should have been provided to you - run `/setup-matt-pocock-skills` 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`, 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