What problem does it solve? Fixing confirmed bugs through a full feature-design workflow is slow and heavy. This Skill provides a lightweight one-approval flow that produces a trimmed Root Cause / Fix / Regression Test spec, then applies the fix — without bypassing governance controls. ## Core Features & Use Cases - One-screen Bug Spec: Drafts a concise spec covering symptom, expected behaviour, root-cause hypothesis, files involved, fix approach, and regression test, gated behind a single APPROVED / EDIT / REJECT cycle. - Governed fix application: Persists the approved spec to docs/Release{R}/Sprint{S}/UserStory{ID}/ before touching source, applies a per-file source-read consent gate, and writes the minimal fix plus a regression test. - Scope guardrails: Redirects anything requiring new endpoints, schema changes, or design decisions to the full ICEA feature flow. - Use Case: A developer runs /bug ADO-2341 "Filter crashes when user has no roles", approves the drafted spec, and gets the null-guard fix plus a regression test filed alongside the Azure DevOps work item. ## Quick Start Run /bug with an Azure DevOps bug ID and a one-line description, for example /bug ADO-2341 "Filter crashes when user has no roles", then approve the drafted spec.