What problem does it solve? Maintainers drown in unstructured issue backlogs where reports lack detail, duplicates resurface, and rejected features get re-requested. This Skill enforces a disciplined triage workflow that categorizes issues, verifies claims against the codebase, and produces durable specifications that autonomous agents can execute. ## Core Features & Use Cases - State machine triage: Move issues and external PRs through category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with conflict detection. - Claim verification: Reproduce reported bugs or check out PR diffs and run tests before recommending a state, so briefs rest on confirmed behavior. - Agent brief generation: Write durable, behavioral specifications with acceptance criteria and scope boundaries that survive codebase refactors. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when similar requests arrive. - Use Case: A maintainer runs triage on issue #42; the Skill reads the thread, checks the codebase for existing implementations, grills the reporter for missing detail, then posts an agent brief and labels the issue ready-for-agent. ## Quick Start Ask the assistant to triage issue #42 and recommend a category and state with reasoning.