What problem does it solve? Debugging often devolves into guesswork, unrelated refactoring, and unverified fixes. This Skill enforces a disciplined workflow that turns an observed failure into a reproducible case, an evidence-backed root cause, and the smallest verified repair. ## Core Features & Use Cases - Structured Root-Cause Isolation: Records expected versus actual behavior, forms falsifiable hypotheses, and runs the cheapest discriminating check one variable at a time. - Regression-First Repair: Requires a failing regression check before applying the production fix, then reruns focused and neighboring validation. - Governed Reporting: Produces reports/debugging-result.json and reports/debugging-result.md distinguishing observations, hypotheses, and confirmed conclusions, with redacted sensitive data. - Use Case: A failing API test points to stale data. Use this Skill to reproduce the failure, isolate an incorrect cache key as the root cause, add a regression test, and verify the focused repair. ## Quick Start Use the systematic-debugging skill to reproduce this failing test, find the root cause, and verify the smallest fix.