What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for evaluating, categorizing, and preparing work for implementation. This Skill enforces a structured triage workflow that turns raw reports into verified, fully specified work items. ## 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. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning rounds to flesh out vague requests before assignment. - Agent brief generation: Write durable, behavior-focused 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 duplicate 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 posts an agent brief so an AFK agent can implement it. ## 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.