Superpowers Systematic Debugging

What This Skill Does

Superpowers Systematic Debugging is a specialized framework designed to enforce a rigorous, four-phase analytical process for technical problem-solving. Moving beyond guesswork, this skill compels the OpenClaw agent to prioritize root cause investigation, pattern analysis, hypothesis testing, and evidence-based verification. It acts as an internal quality gate, preventing the common mistake of 'shotgun debugging,' where quick patches are applied without understanding the underlying failure, often leading to technical debt or new bugs.

Installation

To integrate this debugging methodology into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/axelhu/superpowers-systematic-debugging

Use Cases

This skill should be utilized whenever an agent encounters:

• Persistent test failures or flakiness.
• Unexpected production behavior that defies initial logic.
• Complex integration issues involving multiple services.
• Performance degradation where the bottleneck is not immediately obvious.
• Recurring bugs that have resisted 2+ attempted fixes.

Example Prompts

1. "We are seeing a 500 error on the checkout page intermittently. Please initiate the Superpowers Systematic Debugging process to isolate the root cause before suggesting a fix."
2. "This specific unit test has failed three times in a row despite two previous code patches. Pause and apply the systematic debugging framework to re-evaluate our hypothesis."
3. "The current build is failing with a cryptic dependency error. Use the systematic debug skill to trace the origin of the value and perform a proper root cause analysis."

Tips & Limitations

• Strict Adherence: The skill is designed to be uncompromising. If an agent tries to skip to the fix, remind it that it must complete the 'Root Cause Investigation' phase first.
• The 3-Fix Limit: A critical component is the threshold of 3 failed attempts. If you have tried three times to fix an issue without success, the skill mandates a shift in focus toward architectural review rather than more code changes.
• Not for Trivial Tasks: While robust, this process is intensive. Use it for complex debugging rather than minor formatting changes or simple syntax corrections to maintain efficiency.
• Document Everything: The skill relies on clear documentation of findings. Always ask the agent to summarize its findings after Stage 1 and Stage 2 to ensure transparency in its thought process.