What problem does it solve? Maintainers of open-source or team projects face a constant stream of unstructured bug reports and feature requests. This Skill moves issues through a consistent triage state machine so every issue ends up classified, actionable, and either ready for an AFK agent, ready for a human, waiting on the reporter, or closed with documented reasoning. ## Core Features & Use Cases - State machine triage: Applies one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to every issue, with conflict detection and maintainer confirmation. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria and explicit scope boundaries so AFK agents can implement issues weeks later without stale file references. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear, preventing re-litigation. - Use Case: A maintainer says "Show me anything that needs my attention" and gets three buckets — unlabeled issues, in-progress triage, and needs-info issues with new reporter activity — then picks one to reproduce, grill, and move to ready-for-agent with a complete brief. ## Quick Start Ask the assistant to triage issue number 42 on the repository and recommend a category and state with reasoning.