What problem does it solve? Maintainers of open-source projects face a constant stream of incoming issues and external pull requests that need categorization, verification, and specification before work can begin. This Skill automates the triage workflow, moving items through a consistent state machine so nothing falls through the cracks and every actionable item ends with a clear, durable brief. ## Core Features & Use Cases - State machine triage: Move issues and 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 to confirm claims before investing in specification work. - Agent brief generation: Write durable, behavioral agent briefs with acceptance criteria and scope boundaries that survive codebase changes. - 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 Monday morning, sees three unlabeled issues and one external PR, verifies a reported bug, grills an ambiguous feature request into shape, and closes a duplicate dark-mode request by linking the existing out-of-scope record. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or name a specific issue or PR number to triage it directly.