bug-triage

Prioritize and assign production/QA bug backlog items into sprint plans.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill bug-triage-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/WindXRan/y3td --skill bug-triage-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an open bug backlog into a clear, sprint-ready plan by re-evaluating each bug’s severity versus fix urgency, preventing critical issues from slipping between sprints, and highlighting systemic trend patterns.

Core Features & Use Cases

  • Severity/Priority Reclassification: Maps each bug to objective severity (S1–S4) and recommended priority (P1–P4) using consistent definitions (or a reference file when available).
  • Sprint-Aware Assignment: Assigns fixable P1/P2 bugs to the current sprint when running in sprint mode, or distributes them across current/next sprint/backlog in full mode while avoiding blind “capacity overfill.”
  • Trend & Risk Detection: Detects systemic hotspots (e.g., clusters by system), regression indicators (bugs against completed stories), aged bugs, and flags “critical unassigned” outcomes.

Quick Start

Run bug-triage in sprint mode for the current sprint by instructing the AI: "/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 QA bug backlog for an upcoming sprint?

To prioritize a QA bug backlog for a sprint, bug triage re-evaluates each issue's severity versus fix urgency to generate an actionable sprint plan. It assigns objective S1–S4 severity and P1–P4 priority ratings to prevent critical issues from slipping.

What is the best way to detect regression bugs and systemic hotspots during triage?

Detecting regression bugs and systemic hotspots during triage involves analyzing bug clusters by system and checking issues against completed stories. This process flags aged bugs and critical unassigned outcomes to highlight systemic risk patterns.

How do I assign bugs to current and next sprints without overfilling capacity?

Assigning bugs to current and next sprints without overfilling capacity requires sprint-aware distribution. In full mode, the triage process distributes fixable P1/P2 bugs across current, next, and backlog sprints while actively avoiding blind capacity overfill.

Can I run a quick triage on just the current sprint's bug intake?

You can run a quick triage on current sprint bug intake by using sprint-scoped mode. This mode specifically assigns fixable P1/P2 bugs to the current sprint, making it ideal for sprint-start triage or post-QA bug intake.

Does bug triage require a specific reference file for severity classification?

Bug triage does not strictly require a specific reference file for severity classification, as it applies consistent definitions by default. However, it can load and utilize a reference file when available to map severity and priority accurately.

Why are some critical bugs left unassigned after sprint planning?

Critical bugs may remain unassigned after sprint planning when capacity is reached or systemic patterns require broader intervention. The triage process explicitly flags these critical unassigned outcomes in the final approval-gated report for visibility.