superpowers-systematic-debugging

Systematic debugging enforces root-cause investigation before applying fixes. It uses a four-phase workflow to trace issues to their source across test, production, and integration scenarios, preventing random fixes that create regressions.

Start with Phase 1: Root Cause Investigation to reproduce the issue and document evidence. Follow the four-phase workflow to trace data and apply defense-in-depth validation, avoiding quick symptom fixes under pressure.

Random fixes waste time and create new bugs because they address symptoms. A systematic debugging approach enforces root-cause investigation first, applying multi-layer validation and instrumentation to prevent regressions and resolve issues reliably.

Yes, the four-phase debugging workflow applies to bugs across test, production, and integration scenarios. It provides explicit anti-pattern guidance and guardrails to ensure robust remediation regardless of the environment.

Common debugging anti-patterns include applying quick symptom fixes under pressure instead of tracing data to the root cause. This skill provides explicit guardrails and a phase-driven workflow to avoid these pitfalls and ensure robust remediation.