bug-triage

Classify production bugs by severity and priority for sprint assignment.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill bug-triage-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/bug-triage
Command: npx skills add https://github.com/scomofo/dragon-forge --skill bug-triage-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a growing production bug backlog into an actionable plan by re-evaluating severity versus priority and assigning issues to the right sprint or backlog.

Core Features & Use Cases

  • Bug backlog ingestion: Scans production/qa/bugs/ using prioritized glob patterns and falls back to consolidated logs when needed.
  • Severity-to-priority classification: Applies consistent S1–S4 severity definitions and P1–P4 priority rules to guide decision-making.
  • Sprint context assignment: Reads the latest production/sprints/ plan to assign P1/P2 bugs to the current sprint (or flag overflow).
  • Systemic trend detection: Flags repeated bugs from the same system or regressions against completed stories for targeted re-review.

Quick Start

Run bug-triage in sprint mode to prioritize and assign the most urgent bugs for the current 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 production bug backlog for sprint planning?

To prioritize a bug backlog for sprint planning, you classify open issues by severity and recommended priority, detect systemic trends, and assign urgent bugs to the current sprint or backlog. This ensures release readiness by focusing on the most critical fixes first.

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

Bug severity classifies the technical impact of an issue using S1–S4 definitions, while priority determines the urgency of fixing it using P1–P4 rules. Bug triage applies both classifications together to assign issues to the appropriate sprint or backlog.

How do I detect systemic bug trends in a QA backlog?

Systemic bug trends are detected by flagging repeated bugs from the same system or identifying regressions against completed stories. This trend analysis highlights areas needing targeted re-review before assigning issues to sprints.

When should I re-evaluate bug priority and severity?

You should re-evaluate bug priority and severity during sprint-start triage, after post-acceptance QA re-evaluation, or whenever bug volume crosses a threshold. Ongoing backlog re-prioritization keeps sprint assignments aligned with current release readiness needs.

Can I assign P1 and P2 bugs directly to the current sprint?

Yes, P1 and P2 bugs are assigned to the current sprint by reading the latest sprint plan context. If the volume of high-priority bugs exceeds sprint capacity, the triage process flags the overflow for backlog management.

What is the best way to document bug triage results for release readiness?

The best way to document bug triage results is to generate a gated report written to production/qa/bug-triage-[date].md after approval. This report captures severity classifications, sprint assignments, and systemic trend detections for release tracking.