systematic-debugging

Root-cause analysis identifies the underlying origin of a bug before attempting fixes. A systematic debugging workflow enforces phased progression through investigation, pattern analysis, hypothesis testing, and implementation to prevent wasted time on uninformed changes.

Debugging multi-component systems requires tracing data flow across components using diagnostic tools like file search, terminal execution, and evidence gathering. A four-phase workflow ensures you reproduce the issue, analyze patterns, test hypotheses, and implement verified fixes.

Data flow tracing diagnoses performance issues and build problems by reading error messages, reproducing the issue, and mapping execution paths. The workflow uses search and terminal tools to gather evidence across affected components before forming a hypothesis.

Systematic debugging works independently of test-driven-development scripts. It applies to existing errors, test failures, and unexpected behavior by enforcing evidence-gathering and hypothesis testing before implementation, rather than relying on pre-written test coverage.

Use a structured debugging workflow instead of guessing fixes when facing complex errors, test failures, unexpected behavior, or performance issues across multi-component systems. It enforces phased progression to ensure fixes address verified root causes rather than symptoms.