systematic-debugging

Systematic debugging is a four-phase root-cause investigation process used to diagnose software bugs, test failures, and unexpected behavior before applying fixes. You should use it when troubleshooting failing unit tests, production outages, performance regressions, or multi-component integration issues to ensure reliable, validated resolutions.

To find the root cause of a failing unit test or CI build failure, apply a structured debugging process that analyzes errors, compares patterns, and tests hypotheses. This method uses file search, terminal execution, and sub-agent delegation to gather evidence and enforce checkpoints, preventing premature fixes.

The best way to debug a production outage or performance regression is following a four-phase systematic approach: analyze the error, identify patterns, test hypotheses, and implement a validated fix. It guides tool usage like file reading and terminal commands to ensure safe, reproducible resolutions without architectural blind spots.

Yes, you can use this systematic debugging method for multi-component integration issues. It supports complex investigations by delegating sub-agents to gather evidence across components, enforcing stop-rules and checkpoints to mitigate risks and prevent premature fixes in interconnected systems.

Troubleshooting unexpected behavior often leads to recurring software bugs when developers apply premature fixes before identifying the true root cause. Systematic debugging enforces risk mitigation checkpoints and hypothesis testing to ensure the original error pattern is fully analyzed and the fix is validated.