What problem does it solve?
This Skill prevents game QA and sprint planning from stalling by turning an unstructured open-bug backlog into an actionable, priority-based plan tied to the current sprint’s scope and capacity.
Core Features & Use Cases
- Severity vs. Priority Classification: Separates impact (S1–S4) from urgency (P1–P4) to make triage decisions that are consistent and reviewable.
- Sprint-Aware Assignment: Assigns P1/P2 bugs to the appropriate sprint backlog in sprint mode while flagging “priority overflow” when capacity is tight.
- Systemic Trend Detection: Detects repeated problem patterns (e.g., multiple bugs from the same system, regressions from completed stories) to surface quality issues early.
- Readable Triage Report Output: Produces a dated report at production/qa/bug-triage-[date].md for team visibility and follow-through.
Quick Start
Run bug triage in sprint mode using the command /bug-triage sprint to prioritize the current open bug backlog and assign fixable items to the active sprint.