systematic-debugging

Systematic debugging is a structured root-cause analysis workflow that enforces finding the actual source of errors before proposing fixes. It guides engineers through investigation, pattern analysis, hypothesis testing, and implementation to prevent ineffective symptom repairs.

To debug root causes of CI failures and flaky tests, follow a four-phase workflow: investigate the root cause, analyze patterns, test hypotheses, and implement the fix. This enforces evidence collection and validation before applying any changes.

Fix production incidents by enforcing a four-phase root-cause investigation workflow before implementation. You must gather evidence, analyze patterns, and validate hypotheses to ensure you are fixing the actual failure rather than just repairing surface symptoms.

Before applying a fix during root-cause debugging, you must complete mandatory steps: investigate the root cause, analyze failure patterns, and test hypotheses with evidence. If any phase stalls, return to the investigation phase to avoid symptom repairs.

Yes, systematic debugging works across production failures, CI pipeline failures, and flaky tests. It provides a stable, repeatable process to record evidence, propose verifiable hypotheses, and validate fixes for various unexpected behavior scenarios.