Triage Bugs

Overview

Classify and prioritize a batch of bug reports using a consistent severity matrix and priority framework. The output is a structured, actionable bug triage that enables sprint planning, on-call prioritization, and resource allocation decisions.

Workflow

1. Read project context — Check .chalk/docs/ for:

   • Architecture docs (to map bugs to components)
   • Previous triage reports for consistency
   • Team structure or component ownership docs
   • Any existing severity definitions the team uses

2. Gather bug reports — From $ARGUMENTS and conversation context:

   • If a list of bugs is provided in conversation, use those
   • If a file or document is referenced, read it
   • If pointed to an issue tracker, read available bug details
   • For each bug, extract: title, description, reproduction steps, environment, reporter, date reported