What problem does it solve? Maintainers of open-source or team projects struggle to keep incoming bug reports and feature requests organized, evaluated, and ready for implementation. This Skill moves issues through a structured triage state machine so every issue gets a category, a state, and a clear next action. ## Core Features & Use Cases - State machine triage: Assigns each issue one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix). - Agent brief generation: Writes durable, behavior-focused agent briefs so issues marked ready-for-agent can be picked up by an AFK coding agent without further clarification. - 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 the triage command, sees all unlabeled and needs-triage issues, picks one, and gets a category recommendation, a reproduction attempt for bugs, and a posted agent brief or needs-info comment. ## Quick Start Ask the assistant to triage issue number 42 and recommend a category and state with reasoning.