systematic-debugging
Structured debugging methodology that mandates root cause investigation before attempting any fixes.
- Four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation with mandatory test cases
- Requires completing Phase 1 (evidence gathering, error analysis, data flow tracing) before proposing any fixes; blocks symptom-based patching
- Includes diagnostic instrumentation guidance for multi-component systems and backward call-stack tracing techniques to isolate failure points
- Enforces stopping and questioning architecture after three failed fix attempts, treating repeated failures as a sign of fundamental design problems rather than implementation issues
Systematic Debugging
Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
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
More from obra/superpowers
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
152.3Kusing-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
92.7Kwriting-plans
Use when you have a spec or requirements for a multi-step task, before touching code
91.3Krequesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
80.4Ktest-driven-development
Use when implementing any feature or bugfix, before writing implementation code
79.8Kexecuting-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
74.2K
More in Agent workflows
find-skills
Discover and install skills from skills.sh directly inside an agent session
vercel-labs/skillsagent-browser
Full browser automation: navigate, click, fill forms, extract data, and screenshot
vercel-labs/agent-browserskill-creator
Create, test, and publish new skills from within your agent
anthropics/skillsbrowser-use
Browser automation with visual understanding — interacts with pages based on what it sees
browser-use/browser-usesubagent-driven-development
Orchestrate specialized subagents for different parts of a task
obra/superpowers