What problem does it solve? Maintainers of open-source or team projects 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: Classify issues with category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix), with conflict detection and maintainer overrides. - Agent brief generation: Produce durable, behavior-focused agent briefs with acceptance criteria and scope boundaries so AFK agents can implement issues without re-reading stale discussions. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when similar requests reappear, preventing re-litigation. - Use Case: A maintainer runs triage on a backlog of 20 unlabeled issues; the Skill buckets them by attention needed, reproduces reported bugs, grills reporters for missing detail, and posts ready-for-agent briefs on the actionable ones. ## Quick Start Ask the assistant to triage issue number 42 and recommend a category and state with reasoning.
