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 structured triage state machine so every issue ends up with a clear category, state, and actionable specification. ## Core Features & Use Cases - State machine triage: Moves issues through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with exactly one category (bug or enhancement) and one state per issue. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement issues without re-reading stale context. - 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, reproduces one bug, grills the reporter on another, and moves a well-specified enhancement to ready-for-agent with a complete agent brief. ## Quick Start Ask the assistant to triage issue number 42 and recommend a category and state with reasoning.