skills.rest
solace-ill
solace-illCOMMUNITY
Explore all skills by this author →
GitHub

bug-triage

Triage and prioritize open bugs by severity and priority into a markdown report.

Updated Apr 26, 2026
Search Tags:#issue-tracking#sprint-planning#bug-triage#backlog-management#triage-report#severity-priority
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill bug-triage-solace-ill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/solace-ill/vector-flow --skill bug-triage-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

Core Features & Use Cases

  • Parses arguments to switch between sprint, full, and trend modes and to interpret mode-specific actions.
  • Loads the bug backlog from production/qa/bugs/ or the consolidated logs, then applies sprint context when available.
  • Classifies bugs by severity (S1–S4) and priority (P1–P4) and surfaces systemic deviation signals.
  • Generates a standardized triage report saved to production/qa/bug-triage-[date].md for handoff.

Quick Start

Run /bug-triage sprint at the start of a sprint to triage current open bugs using the latest backlog and sprint context.

Frequently Asked Questions about bug-triage

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

FAQPage Schema
How do I triage bugs and prioritize a QA backlog for sprint planning?▼

Triage bugs by evaluating issue severity versus priority across the production QA backlog to generate a sprint-ready triage report. It classifies open bugs using S1-S4 and P1-P4 rules, then outputs a standardized markdown file for sprint planning handoff.

What is the best way to surface systemic bug trends across multiple sprints?▼

Surfacing systemic bug trends is done by running a trend mode analysis on the consolidated bug logs. It evaluates severity and priority deviations across the production QA backlog to identify recurring issues and outputs the findings into a dated markdown triage report.

How does severity versus priority classification work for issue tracking?▼

Severity versus priority classification works by applying predefined rules to categorize open bugs from S1-S4 for severity and P1-P4 for priority. This mechanism re-evaluates the production QA backlog to ensure consistent prioritization and surfaces systemic deviation signals for sprint planning.

Can I generate a triage report using existing sprint context and open bugs?▼

You can generate a triage report by loading open bugs from the production QA backlog and applying available sprint context from production sprints. Running in sprint mode triages current issues against the active sprint, producing a markdown report for team handoff.

When should I run a full bug triage instead of a sprint triage?▼

Run a full bug triage when the open bug count grows significantly and requires complete re-prioritization across the entire backlog. Sprint mode is for routine sprint start planning, while full mode comprehensively evaluates all accumulated open bugs and severity deviations.

Does bug triage require external dependencies to manage backlog issues?▼

Bug triage requires no external dependencies, operating directly on local production QA bug logs and sprint context. It parses the internal backlog structure to apply severity and priority classifications, generating a self-contained markdown triage report.

Related Skills

Explore More Software Engineering Skills→
packetalienpacketalien

bug-triage

Triage open bug reports into prioritized, sprint-assigned Markdown action lists.

Community
Advanced
emcconnellemcconnell

bug-triage

Classify markdown bug reports into prioritized sprint-aware triage reports.

Community
Advanced
maslennikov-igmaslennikov-ig
243

calculate-priority-score

Calculate numeric priority scores from severity, impact, and likelihood.

Community
Intermediate
OreStudioOreStudio
25

agile-product-owner

Create and prioritize user stories across ORE Studio sprint and product backlogs.

Official
Basic