systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Install
With your agent
Install OMGSkills skill "obra/superpowers:systematic-debugging" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/obra/superpowers /tmp/superpowers && ln -s /tmp/superpowers/skills/systematic-debugging ~/.claude/skills/systematic-debuggingFrom README
Systematic Debugging Overview Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure. Violating the letter of this process is violating the spirit of debugging. The Iron Law If you haven't completed Phase 1, you cannot propose fixes. When to Use Use for ANY technical issue: Test failures Bugs in production Unexpected behavior Performance problems Build failures Integration issues Use this ESPECIALLY when: Under time pressure (emergencies make guessing tempting) "Just one quick fix" seems obvious You've already tried multiple fixes Previous fix didn't work You don't fully understand the issue Don't skip when: Issue seems simple (simple bugs have root causes too) You're in a hurry (rushing guarantees rework) Manager wants it fixed NOW (systematic is faster than thrashing) The Four Phases You MUST complete each phase before proceeding to the next.
More from this repo
executing-plans
Used when executing an implementation plan in the current session as the implementer yourself — your human partner...
subagent-driven-development
Used when executing implementation plans with independent tasks in the current session
writing-skills
Used when creating new skills, editing existing skills, or verifying skills work before deployment