bug-triage

Prioritizes sprint assignments for production/QA bugs from parsed bug markdown files.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill bug-triage-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill bug-triage-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the confusion of unmanaged bug backlogs by systematically re-evaluating severity vs. priority, assigning the right issues to the right sprint, and surfacing systemic problem trends.

Core Features & Use Cases

  • Sprint-aware prioritization: Assigns P1/P2 bugs to the current sprint backlog when running in sprint mode, or distributes them across current/next sprint and backlog in full mode.
  • Severity vs. priority classification: Uses objective severity definitions (S1–S4) and urgency-based priority definitions (P1–P4) to produce actionable triage outputs.
  • Systemic trend detection: Flags potential quality/system issues when multiple related bugs cluster in the same area or when regressions appear in completed stories.
  • Triage reporting & gating: Generates a triage report and gates actions via an explicit “ask before writing” protocol, including special handling for unassigned S1 bugs and regressions.

Quick Start

Tell the agent to triage the current production/qa bug backlog for sprint planning by running: /bug-triage sprint

Frequently Asked Questions about bug-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize a bug backlog for sprint planning?

Bug backlog prioritization for sprint planning is achieved by re-evaluating severity versus urgency and classifying issues into S1–S4 and P1–P4 categories. The skill assigns P1/P2 bugs to the current sprint and generates an actionable triage report.

What is the difference between bug severity and priority during triage?

The difference between bug severity and priority during triage is that severity uses objective S1–S4 definitions to measure impact, while priority uses urgency-based P1–P4 definitions to determine sprint assignment and immediate action.

How do I detect systemic quality issues and regressions in completed stories?

Systemic quality issues and regressions in completed stories are detected by flagging clusters of multiple related bugs in the same area. The triage process surfaces these systemic trends to highlight potential quality problems.

Can I assign open production and QA bugs to sprints in full mode versus sprint mode?

You can assign open production and QA bugs to sprints differently by mode: sprint mode assigns P1/P2 bugs only to the current sprint, while full mode distributes issues across the current sprint, next sprint, and backlog.

When should I run bug triage on my QA backlog?

You should run bug triage on your QA backlog during sprint-start re-prioritization, immediately after new QA bug filing batches, or whenever the open bug count indicates that systematic triage is needed.

Does bug triage automatically write sprint changes to my production files?

Bug triage does not automatically write sprint changes to production files. It generates a triage report and gates all write actions behind an explicit user approval protocol before modifying any output.