superpowers-debugging

Root-cause debugging systematically traces data flow and gathers evidence to identify the origin of a bug before implementing fixes. It enforces a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.

Debugging intermittent production failures requires structured investigation to reliably reproduce the issue and trace data flow across services. A phased workflow ensures evidence gathering and pattern analysis precede any remediation planning or guarded changes.

Triage flaky CI builds by reproducing errors consistently and analyzing failure patterns before proposing changes. Establishing a verifiable hypothesis through evidence gathering prevents misdirected fixes and ensures the root cause is addressed.

Root-cause debugging applies across both single-module codebases and multi-service environments. The structured investigation workflow scales from tracing local test failures to triaging complex production incidents and CI pipeline issues.

Systematically trace unexpected software behavior through four phases: gather evidence and reproduce the issue during Root Cause Investigation, perform Pattern Analysis, form hypotheses in the Testing phase, and execute guarded changes during Implementation.

Avoid jumping to implementation when unexpected software behavior lacks verifiable evidence. Applying fixes before completing root cause investigation and hypothesis testing risks misdirected remediation and unresolved underlying issues.