What problem does it solve? Maintainers of open-source projects face a constant stream of incoming issues and external pull requests that need categorization, verification, and specification before work can begin. This Skill automates the triage workflow so every issue ends up with a clear category, a defined state, and either an actionable brief or a documented rejection. ## Core Features & Use Cases - State machine triage: Moves issues and PRs through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with category labels (bug, enhancement). - Verification and grilling: Reproduces reported bugs, checks out PR diffs to confirm claims, and asks targeted questions to flesh out vague requests. - Agent brief generation: Writes 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: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues and one external PR, verifies a reported bug, sends one issue back for more info, and publishes an agent brief for a confirmed enhancement. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or name a specific issue number to triage it end to end.