
Systematic Debugging
Forces you to investigate root causes before attempting any fixes through a rigid four-phase process: evidence gathering with diagnostic logging at component boundaries, pattern analysis against working examples, hypothesis testing with minimal changes, and proper test-driven implementation. Specifically prevents the "quick fix" trap by requiring you to trace data flow, add instrumentation to multi-layer systems, and stop after three failed attempts to question the underlying architecture. Most useful when you're under pressure and tempted to guess, or when dealing with complex systems where symptoms appear far from causes.
- install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.
- 142
- skills.sh installs
- 326.7K
- GitHub stars
- 315.2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add obra/superpowers --skill systematic-debugging --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
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.
Phase 1: Root Cause Investigation
BEFORE attempting ANY fix:
Sponsors
Details
- Repository
- github.com/obra/superpowers
- Categories
- Testing & QA, Debugging
More from obra/superpowers
All 14- Writing Plans298.6K
- Using Superpowers283.7K
- Requesting Code Review276.5K
- Test Driven Development274.8K
- Verification Before Completion270.3K
- Executing Plans257.5K
- Subagent Driven Development252K
- Receiving Code Review235.1K
- Dispatching Parallel Agents231.3K
- Writing Skills231.3K
- Using Git Worktrees230.2K
- Finishing A Development Branch227.7K
- Brainstorming423.3K