What problem does it solve? Maintainers drown in unlabeled issues and external PRs that lack clear categorization, verification, and actionable specifications. This Skill moves each item through a defined state machine of triage roles so every issue ends up categorized, verified, and either ready for an agent, ready for a human, or closed with documented reasoning. ## Core Features & Use Cases - State machine triage: Apply category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to issues and external PRs, with conflict detection and maintainer confirmation. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, check for redundant existing implementations, and run structured questioning rounds to flesh out vague requests. - Agent briefs and out-of-scope records: Write durable, behavior-focused agent briefs with acceptance criteria, and record rejected enhancements in a .out-of-scope/ knowledge base to deduplicate future requests. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled GitHub issues; each one gets categorized, verified against the codebase, and either receives an agent-ready brief, a needs-info request to the reporter, or a documented wontfix closure. ## 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 end to end.