systematic-debugging

Systematic debugging is a four-phase framework enforcing root-cause investigation before fixes. You need it during production incidents, bug triage, or flaky tests to prevent symptom-focused patches and identify the actual underlying failure.

To debug flaky test failures, execute a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation. This enforces a mandatory investigation phase before proposing any code changes to verify the fix targets the actual defect.

To stop applying symptom-focused patches, enforce a mandatory root-cause investigation phase before proposing fixes. This prevents wasted effort by requiring pattern analysis and hypothesis testing to validate the underlying failure mechanism.

Yes, this systematic debugging approach works for performance issues and operations contexts. It applies across software development and operations, guiding teams through root cause investigation, pattern analysis, hypothesis testing, and implementation for any complex incident.

Common anti-patterns to avoid during root-cause analysis include skipping the mandatory investigation phase and proposing fixes before testing hypotheses. The framework provides explicit checklists and anti-pattern guidance to prevent these wasted effort scenarios.

Yes, you can integrate root-cause tracing and test-driven development with this debugging workflow. The framework explicitly integrates with these related skills to connect hypothesis testing and implementation phases with existing testing and tracing operations.