systematic-debugging

Systematic debugging enforces a four-phase root-cause investigation process before applying any fixes, preventing symptom-focused patches. It is needed for complex multi-component systems and time-constrained production incidents to ensure robust, repeatable investigations.

To debug production incidents without fixing symptoms, follow a strict four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. Mandatory Phase 1 investigation prevents wasted effort on random fixes before the actual root cause is identified.

The best way to structure a debugging workflow is using a phase-driven approach with explicit rules and defense-in-depth across layers. This ensures you complete Pattern Analysis and Hypothesis Testing phases before implementation, which is critical for diagnosing complex multi-component systems.

Random fixing wastes time and creates new bugs because it addresses symptoms rather than root causes. Applying anti-patterns like jumping straight to fixes skips the required root-cause analysis, leading to repeatable investigations failing and wasted debugging effort.

Yes, you can use defense-in-depth across layers to prevent symptom-focused fixes. By enforcing explicit rules and a STOP-and-re-analyze anti-pattern defense, the debugging process ensures robust investigations and prevents applying patches that mask the underlying root cause.

To start a root-cause investigation, load the systematic debugging skill and immediately begin with Phase 1: Root Cause Investigation. You must complete this mandatory phase to identify the true root cause before proposing any fixes or moving to Pattern Analysis and Hypothesis Testing.