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 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/skillsbrainstorming
Structured ideation and problem decomposition frameworks
obra/superpowersbrowser-use
Browser automation with visual understanding — interacts with pages based on what it sees
browser-use/browser-use