What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for categorizing, verifying, and routing them. This Skill enforces a structured triage workflow so every issue ends up with a clear category, state, and actionable specification. ## Core Features & Use Cases - State machine triage: Move issues and PRs through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with category roles (bug or enhancement). - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and ask targeted questions to flesh out vague requests. - Agent brief generation: Write durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement changes without re-reading the whole thread. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when similar requests arrive. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues, verifies one bug by reproducing it, moves it to ready-for-agent with a complete brief, and closes a duplicate feature request by linking to an existing out-of-scope record. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, then pick an issue to evaluate.