What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for categorizing, verifying, and routing them. This Skill enforces a structured triage workflow so every issue gets a category, a state, and either an actionable brief or a clear reason for closure. ## Core Features & Use Cases - State machine triage: Move issues and PRs through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with bug/enhancement categories. - Verification and grilling: Reproduce reported bugs, validate PR diffs, and ask targeted clarifying questions before committing to a state. - Agent brief generation: Write durable, behavior-focused agent briefs with acceptance criteria 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, requests reproduction steps on another, and publishes an agent brief for a well-specified enhancement. ## 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.