Systematic Debugging

Systematic Debugging teaches a disciplined four-phase process for tackling any technical issue—from test failures to production bugs. By enforcing root cause investigation before attempting fixes, it eliminates guesswork and the cycle of symptom-patching that creates new problems. The framework emphasizes evidence gathering, pattern analysis, hypothesis testing, and architectural questioning when multiple fixes fail.

Systematic Debugging enforces a disciplined four-phase process: investigate root cause, analyze patterns, form and test hypotheses, then implement fixes. It stops you from guessing or patching symptoms, ensuring you understand the actual problem before making changes.

This skill enforces a disciplined debugging methodology that prioritizes root cause discovery over quick patches. Work through four phases—investigation, pattern analysis, hypothesis testing, and implementation—completing each before advancing. The framework prevents the trap of symptom-fixing by requiring evidence gathering across component boundaries and data flow tracing before any fix attempt.

Debugging provides structured methodologies across four sub-skills: systematic investigation to isolate root causes, backward tracing through call stacks, layered validation to prevent recurrence, and verification before claiming fixes are complete. Use it when encountering bugs, test failures, or unexpected behavior.

Diagnostic Analysis guides you through a four-phase debugging methodology that prioritizes root cause investigation over quick fixes. It emphasizes gathering evidence in multi-component systems, comparing working patterns, forming testable hypotheses, and implementing targeted solutions—stopping to question architecture if multiple fixes fail.

This skill systematically investigates why problems occur by separating genuine causal relationships from correlations and symptoms. It guides you through defining effects, generating competing hypotheses, building causal models, testing causality rigorously, and documenting findings with confidence levels. Apply it to incident investigations, metric changes, policy evaluation, or debugging.