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.* ``` ## Second-dev cold-pickup rule Every issue this skill promotes to `ready-for-agent` (or `ready-for-human`) must contain enough context that a **second dev** — teammate, AFK agent, or returning maintainer — who has never seen the conversation can act on it cold. Acceptance criteria must be inline and machine-checkable where possible. The atomic `## Agent Brief` comment is the contract surface; the linked issue body is context, not specification. Rationale: ai-kit defaults assume ≥2 devs (one writer, one reviewer), per ai-kit issue #52. Issues prepared for cold-pickup keep that invariant honest even when the second dev is part-time or AI. If the brief cannot stand on its own, route to `needs-info` instead. ## 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 -