What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for classifying, verifying, and routing them. This Skill enforces a structured triage workflow so every issue gets a category, a state, and—when ready—a durable agent brief that an autonomous agent can execute against. ## Core Features & Use Cases - State machine triage: Routes issues and PRs through canonical roles (bug/enhancement × needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with conflict detection. - Verification and grilling: Reproduces reported bugs, checks out PRs to confirm diffs, checks for redundant implementations and prior rejections in .out-of-scope/, then grills vague requests into shape. - Durable agent briefs: Writes behavioral, path-independent briefs with acceptance criteria so AFK agents can execute work weeks later. - Use Case: A maintainer runs /triage on Monday, sees three buckets of items needing attention, picks issue #42, verifies the reported bug, and posts an agent brief that an autonomous coding agent picks up the next day. ## Quick Start Ask the assistant to triage issue #42 on the repository's issue tracker and recommend a category and state.