bug-triage

Classify game bugs by severity and priority, assign sprints, and generate triage reports.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill bug-triage-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/bug-triage
Command: npx skills add https://github.com/MichaelSolati/mkai --skill bug-triage-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often struggle with growing bug backlogs that are time-consuming to manually prioritise and assign, leading to critical issues being overlooked, sprint capacity being mismanaged, and systemic quality problems going undetected until they cause larger release delays.

Core Features & Use Cases

  • Severity & Priority Classification: Automatically distinguishes between bug impact (severity) and fix urgency (priority) to ensure critical issues are addressed first.
  • Sprint Assignment & Capacity Management: Assigns bugs to current or upcoming sprints based on team capacity, flags overflow to prevent overcommitment.
  • Systemic Trend Detection: Identifies hot spot systems, regression bugs from completed stories, and aged high-severity bugs to surface underlying quality issues.
  • Use Case: For a game team with 12 open bugs at the start of a new sprint, use this skill to automatically triage all bugs, assign P1 critical issues to the current sprint, and flag any recurring bugs in the combat system as a potential systemic quality issue.

Quick Start

Use the bug-triage skill to triage all open game bugs against the current sprint and generate a prioritised triage report.

Frequently Asked Questions about bug-triage

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

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

Automatically prioritizing a game bug backlog for sprint planning involves classifying bugs by severity and priority, then assigning them to sprints based on team capacity to prevent overcommitment while ensuring critical issues are addressed first.

What is the difference between bug severity and priority in game quality assurance?

In game quality assurance, bug severity distinguishes the impact of a bug on the game, while priority determines the fix urgency. Separating these metrics ensures critical issues are scheduled correctly without mismanaging sprint capacity.

How do I track systemic quality trends and regression bugs across game development sprints?

Tracking systemic quality trends and regression bugs across game development sprints requires analyzing the bug backlog to identify hot spot systems, aged high-severity bugs, and regressions from completed stories. This surfaces underlying quality issues before they cause release delays.

When should I use automated bug triage for my game development workflow?

You should use automated bug triage in your game development workflow at the start of a sprint, following QA bug filing cycles, or when open bug counts exceed 10. This prevents critical issues from being lost between sprints and avoids manual backlog overload.

Can bug triage prevent sprint capacity overallocation when assigning open game bugs?

Yes, bug triage prevents sprint capacity overallocation when assigning open game bugs by enforcing guardrails against overcommitment. It evaluates team capacity and flags overflow, ensuring that only appropriate bugs are assigned to current or upcoming sprints.

What guardrails are enforced during automated bug triage to protect the sprint backlog?

Guardrails enforced during automated bug triage to protect the sprint backlog include preventing unapproved bug closure and blocking sprint capacity overallocation. These constraints ensure bugs are securely assigned without disrupting current development commitments.