What problem does it solve?
Triaging open bugs is time-consuming and error-prone. This skill automates the evaluation of bug severity versus priority, assigns items to the appropriate sprint or backlog, and surfaces systemic trends to guide QA and development planning.
Core Features & Use Cases
- Load and parse bug backlog from production/qa/bugs/*.md or the consolidated production/qa/bugs.md log.
- Classify each bug by Severity (S1-S4) and Priority (P1-P4) with deviation checks to surface patterns.
- Assign bugs to the current sprint or backlog based on the selected mode (/bug-triage sprint, full, or trend) and available sprint capacity.
- Perform trend analysis for volume, hot spots, age, and regressions, then generate a triage report.
- Output the triage results to production/qa/bug-triage-[date].md and gate report creation.
Quick Start
Run /bug-triage sprint to triage current bugs for the active sprint and generate a triage report.