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 that turns raw reports into agent-ready briefs, human-ready tasks, or documented rejections. ## 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) with conflict resolution and precedence rules. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning to flesh out vague requests before routing them. - Agent brief generation: Write durable, behavior-focused agent briefs with acceptance criteria and scope boundaries, following the AGENT-BRIEF.md reference. - Out-of-scope knowledge base: Record rejected enhancements in .out-of-scope/ files and deduplicate repeat requests against prior decisions. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled GitHub issues; the Skill buckets them by attention needed, verifies each bug claim against the codebase, and posts agent-ready briefs for the ones that are fully specified. ## Quick Start Ask the assistant to triage issue #42 or show everything on the tracker that needs attention.