bug-triagelisted

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.
NITISH-R-G/skills-i-use · ★ 1 · AI & Automation · score 65

Install: claude install-skill NITISH-R-G/skills-i-use

# Bug Triage This skill processes the open bug backlog into a prioritised, sprint-assigned action list. It distinguishes between **severity** (how bad is the impact?) and **priority** (how urgently must we fix it?), detects systemic trends, and ensures no critical bug is lost between sprints. **Output:** `production/qa/bug-triage-[date].md` **When to run:** - Sprint start — assign open bugs to the new sprint or backlog - After `/team-qa` completes and new bugs have been filed - When the bug count crosses 10+ open items --- ## 1. Parse Arguments **Modes:** - `/bug-triage sprint` — triage against the current sprint; assign fixable bugs to the sprint backlog; defer the rest - `/bug-triage full` — full triage of all bugs regardless of sprint scope - `/bug-triage trend` — trend analysis only (no assignment); read-only report - No argument — run sprint mode if a current sprint exists, else full mode --- ## 2. Load Bug Backlog ### Step 2a — Discover bug files Glob for bug reports in priority order: 1. `production/qa/bugs/*.md` — individual bug report files (preferred format) 2. `production/qa/bugs.md` — single consolidated bug log (fallback) 3. Any `production/qa/qa-plan-*.md` "Bugs Found" table (last resort) If no bug files found: > "No bug files found in `production/qa/bugs/`. If bugs are tracked in a > different location, adjust the glob pattern. If no bugs exist yet, there is > nothing to triage." Stop and report. Do not proceed if no bugs exist. ### Step 2b — Loa