Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Security grade of this SKILL.md: SAFE · how we grade
How to install systematic-debugging
npx skills add obra/superpowers --skill systematic-debugging -a claude-code
The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.
What the SKILL.md says
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. If you haven't completed Phase 1, you cannot propose fixes. 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). You MUST complete each phase before proceeding to the next. BEFORE attempting ANY fix: Read Error Messages Carefully.
Other skills in obra/superpowers
brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning…
diagnosing-superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results,…
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plansUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, o…
finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work
receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable…
requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current session
test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated w…
using-superpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clari…
verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and…
writing-plansUse when you have a spec or requirements for a multi-step task, before touching code
writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment