What problem does it solve?
Unstructured GitHub issue triage leads to inconsistent labeling, duplicated work, and issues stuck in limbo without clear ownership or next steps, wasting maintainer time and delaying project progress.
Core Features & Use Cases
- Standardized State Machine Triage: Enforce consistent bug/enhancement categorization and state progression (needs-triage, ready-for-agent, wontfix, etc.) across all project issues.
- Durable Agent Brief Generation: Create implementation-agnostic, context-rich specs for AFK agents that remain useful even as the codebase evolves.
- Out-of-Scope Knowledge Base: Track rejected feature requests with decision reasoning to prevent duplicate re-litigation and preserve institutional memory.
- Use Case: A maintainer handling 50+ monthly GitHub issues can use this skill to automate triage workflows, ensure consistent labeling, prepare clear handoff specs for autonomous agents, and avoid rehashing previously rejected feature requests.
Quick Start
Use the triage skill to review all unlabeled and needs-triage GitHub issues and generate a prioritized list of items requiring your attention.