superpowers-systematic-debugging

Apply a four-phase systematic debugging framework centered on root-cause investigation.

Updated Dec 16, 2025

Search Tags:#debugging #defense-in-depth #systematic #phases #root-cause #root-cause-tracing

Ready to run

npx skills add https://github.com/fegome90-cmd/fork_agent --skill superpowers-systematic-debugging-fegome90-cmd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-systematic-debugging
Source: https://github.com/fegome90-cmd/fork_agent/tree/main/.kilocode/skills/superpowers-systematic-debugging
Command: npx skills add https://github.com/fegome90-cmd/fork_agent --skill superpowers-systematic-debugging-fegome90-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bugs and flaky behavior waste time and create rework; this skill enforces a disciplined four-phase process that centers on root-cause investigation before proposing any fixes.

Core Features & Use Cases

Phase-driven workflow from Phase 1 (Root Cause Investigation) to Phase 4 (Implementation)
Anti-shortcut guards and defense-in-depth patterns to prevent symptom fixes
Applies to debugging scenarios ranging from test failures to production incidents and integration issues

Quick Start

Follow Phase 1: Root Cause Investigation before attempting any fixes, then proceed through Phases 2–4 as described.

Frequently Asked Questions about superpowers-systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is systematic debugging and how does root-cause tracing work?▼

Systematic debugging enforces a structured four-phase framework centered on root-cause investigation. It uses a scientific hypothesis-and-testing cycle to identify the true source of failures before proposing or implementing any fixes.

How do I debug production incidents without rushing to apply symptom fixes?▼

To debug production incidents safely, follow a disciplined four-phase process starting with root-cause investigation. Anti-shortcut guards prevent premature symptom fixes, ensuring you resolve the actual underlying issue first.

What is the best way to stop flaky test failures from reoccurring in integration environments?▼

The best way to stop flaky test failures is applying a systematic debugging framework with defense-in-depth patterns. By completing root-cause investigation before fixes, you prevent regressions and eliminate recurring integration issues.

How do I systematically trace a root cause for a complex bug?▼

Trace a root cause by following Phase 1 of the systematic debugging framework, which mandates a scientific hypothesis-and-testing cycle. You must complete this investigation phase fully before moving to implementation and fixes.

When should I escalate a bug that keeps failing after multiple fixes?▼

You should escalate a bug during systematic debugging when multiple fixes fail to resolve the issue. The framework includes built-in escalation triggers to prevent endless cycles of ineffective patches.

Can I use this systematic debugging approach for both test failures and production incidents?▼

Yes, this systematic debugging approach applies to test failures, production incidents, and integration issues. The four-phase framework scales across different debugging scenarios to ensure thorough root-cause investigation.