What problem does it solve? Maintainers of active repositories face a constant stream of incoming bug reports and feature requests that need consistent classification, reproduction, and specification before work can begin. This Skill moves issues through a defined state machine of triage roles so every issue ends up clearly categorized, actionable, and ready for either a human or an autonomous agent. ## Core Features & Use Cases - State machine triage: Classifies issues with one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix), surfacing anything needing maintainer attention. - Agent brief authoring: Produces durable, behavior-focused agent briefs with concrete acceptance criteria and explicit scope boundaries so AFK agents can execute without stale file-path references. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and matches new issues against prior rejections to avoid re-litigating decisions. - Use Case: A maintainer says "Show me anything that needs my attention" and receives three buckets of unlabeled, in-progress, and reporter-updated issues, then moves issue #42 to ready-for-agent with a complete agent brief posted as a comment. ## Quick Start Ask the assistant to use the triage skill to show which GitHub issues currently need maintainer attention.
