What problem does it solve? Maintainers drown in unlabeled issues and external PRs that lack clear categorization, verification, and actionable specifications. This Skill structures the entire triage workflow so every issue ends up with a clear category, state, and either an agent-ready brief or a documented rejection. ## Core Features & Use Cases - State machine triage: Move issues and PRs through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with category labels (bug, enhancement). - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning rounds to flesh out vague requests. - Agent brief generation: Write durable, behavioral agent briefs with acceptance criteria and scope boundaries for AFK agents to execute. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and deduplicate new requests against prior rejections. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues and one external PR, verifies a reported bug, converts a feature request into an agent brief, and closes a duplicate dark-mode request by referencing the existing out-of-scope record. ## 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 directly.