What problem does it solve? It prevents premature fixes by enforcing a disciplined debugging sequence: no change is proposed until the failure is reproduced and its root cause is named, eliminating symptom-masking patches and stacked guesswork. ## Core Features & Use Cases - Six-step root-cause workflow: Reproduce with a deterministic trigger, collect evidence, isolate the failing boundary, test one hypothesis at a time, fix the root cause, and add a regression check. - Hypothesis discipline: One variable at a time, never stacked fixes, and a hard stop after three failed hypotheses to question the design instead. - Current-state recording: The durable record carries only the reproduction, evidence, root cause, fix, and regression check — no investigation diary. - Use Case: An intermittent production failure tempts a quick retry patch before a deadline; the skill requires reproducing the failure and naming the cause, shipping a retry only as a labelled mitigation for an external cause. ## Quick Start Debug this failing test by first reproducing it, isolating the failing boundary, and identifying the root cause before proposing any fix.
