bug-triage

Prioritize open bug backlogs into sprint work with triage reports.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill bug-triage-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/bug-triage
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill bug-triage-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn a growing bug backlog into a clear, defensible action plan by re-evaluating severity, priority, sprint fit, and systemic risk before work starts to pile up.

Core Features & Use Cases

  • Backlog triage: Reads open bug reports from the standard bug locations and classifies them by severity and urgency.
  • Sprint assignment: Maps fixable P1/P2 issues to the current sprint or next sprint based on capacity and scope.
  • Trend analysis: Surfaces hotspots, regressions, aging defects, and repeated systemic issues across the backlog.
  • Report generation: Produces a structured triage report that can be reviewed before any write action is taken.
  • Use Case: A QA lead can run this Skill at sprint start to decide which bugs must be fixed immediately, which should wait, and where recurring quality problems are emerging.

Quick Start

Use the bug-triage skill to review the current bug backlog and produce a prioritized triage report for the active 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 involves re-evaluating open defects by severity, priority, sprint capacity, and regression risk to generate assignment recommendations and a structured triage report.

What is bug triage and how does it classify open defects?

Bug triage is the process of reading open bug reports and classifying defects by severity and urgency, mapping fixable P1/P2 issues to sprints based on capacity, and surfacing aging defects or regressions.

Can I analyze bug severity and regression risk trends across my backlog?

Yes, trend analysis across a bug backlog surfaces quality hotspots, repeated systemic issues, aging defects, and regressions, providing metrics that inform which defects require immediate attention.

Does bug triage automatically assign issues to the current sprint?

Bug triage maps fixable P1/P2 issues to the current or next sprint based on capacity and scope, but it generates a write-gated report first so assignments are reviewed before any write action is taken.

What is the best way to turn growing bug reports into sprint-ready priorities?

The best way to turn growing bug reports into sprint-ready priorities is to re-evaluate severity, sprint fit, and systemic risk, then produce a defensible action plan with assignment recommendations before work starts.

When should I not use automated bug triage for defect backlog review?

Automated bug triage for defect backlog review should not be used as the sole decision maker; it is designed to produce a structured triage report requiring human review before any write action or sprint assignment is executed.