systematic-debugging

Systematic debugging identifies the true root cause of bugs by tracing data flow across multi-component systems. It enforces a four-phase approach: root-cause investigation, pattern analysis, hypothesis testing, and implementation verification to stop guessing.

To find the root cause of a production incident, reproduce the failing behavior reliably, trace data flow back to the original trigger, and apply pattern analysis. Use reference templates to guide instrumentation and validate fixes across services.

The best way to diagnose test failures is applying a phase-driven approach: investigate root causes, analyze patterns, test hypotheses, and verify implementation. This structured method ensures you trace evidence rather than relying on guesswork.

Yes, systematic debugging works for performance issues and integration problems in multi-service architectures. It provides structured methods for tracing data flow, collecting evidence, and validating fixes across complex distributed systems.

Validate fixes during root-cause analysis by applying defense-in-depth principles and implementation verification. Use provided templates like defense-in-depth.md and condition-based-waiting.md to guide instrumentation and establish guardrails for validated testing.