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
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:
Read Error Messages Carefully
- Don't skip past errors or warnings
- They often contain the exact solution
- Read stack traces completely
- Note line numbers, file paths, error codes
Reproduce Consistently
- Can you trigger it reliably?
- What are the exact steps?
- Does it happen every time?
- If not reproducible → gather more data, don't guess
Check Recent Changes
- What changed that could cause this?
- Git diff, recent commits
- New dependencies, config changes
- Environmental differences
Gather Evidence in Multi-Component Systems
WHEN system has multiple components (CI → build → signing, API → service → database):
BEFORE proposing fixes, add diagnostic instrumentation:
For EACH component boundary:
- Log what data enters component
- Log what data exits component
- Verify environment/config propagation
- Check state at each layer
Run once to gather evidence showing WHERE it breaks
THEN analyze evidence to identify failing component
THEN investigate that specific component
Example (multi-layer system):
# Layer 1: Workflow
echo "=== Secrets available in workflow: ==="
echo "IDENTITY: ${IDENTITY:+SET}${IDENTITY:-UNSET}"
# Layer 2: Build script
echo "=== Env vars in build script: ==="
env | grep IDENTITY || echo "IDENTITY not in environment"
# Layer 3: Signing script
echo "=== Keychain state: ==="
security list-keychains
security find-identity -v
# Layer 4: Actual signing
codesign --sign "$IDENTITY" --verbose=4 "$APP"
This reveals: Which layer fails (secrets → workflow ✓, workflow → build ✗)
Trace Data Flow
WHEN error is deep in call stack:
See root-cause-tracing.md in this directory for the complete backward tracing technique.
Quick version:
- Where does bad value originate?
- What called this with bad value?
- Keep tracing up until you find the source
- Fix at source, not at symptom
Phase 2: Pattern Analysis
Find the pattern before fixing:
Find Working Examples
- Locate similar working code in same codebase
- What works that's similar to what's broken?
Compare Against References
- If implementing pattern, read reference implementation COMPLETELY
- Don't skim - read every line
- Understand the pattern fully before applying
Identify Differences
- What's different between working and broken?
- List every difference, however small
- Don't assume "that can't matter"
Understand Dependencies
- What other components does this need?
- What settings, config, environment?
- What assumptions does it make?
Phase 3: Hypothesis and Testing
Scientific method:
Form Single Hypothesis
- State clearly: "I think X is the root cause because Y"
- Write it down
- Be specific, not vague
Test Minimally
- Make the SMALLEST possible change to test hypothesis
- One variable at a time
- Don't fix multiple things at once
Verify Before Continuing
- Did it work? Yes → Phase 4
- Didn't work? Form NEW hypothesis
- DON'T add more fixes on top
When You Don't Know
- Say "I don't understand X"
- Don't pretend to know
- Ask for help
- Research more
Phase 4: Implementation
Fix the root cause, not the symptom:
Create Failing Test Case
- Simplest possible reproduction
- Automated test if possible
- One-off test script if no framework
- MUST have before fixing
- Use the
superpowers:test-driven-development skill for writing proper failing tests
Implement Single Fix
- Address the root cause identified
- ONE change at a time
- No "while I'm here" improvements
- No bundled refactoring
Verify Fix
- Test passes now?
- No other tests broken?
- Issue actually resolved?
If Fix Doesn't Work
- STOP
- Count: How many fixes have you tried?
- If < 3: Return to Phase 1, re-analyze with new information
- If ≥ 3: STOP and question the architecture (step 5 below)
- DON'T attempt Fix #4 without architectural discussion
If 3+ Fixes Failed: Question Architecture
Pattern indicating architectural problem:
- Each fix reveals new shared state/coupling/problem in different place
- Fixes require "massive refactoring" to implement
- Each fix creates new symptoms elsewhere
STOP and question fundamentals:
- Is this pattern fundamentally sound?
- Are we "sticking with it through sheer inertia"?
- Should we refactor architecture vs. continue fixing symptoms?
Discuss with your human partner before attempting more fixes
This is NOT a failed hypothesis - this is a wrong architecture.
Red Flags - STOP and Follow Process
If you catch yourself thinking:
- "Quick fix for now, investigate later"
- "Just try changing X and see if it works"
- "Add multiple changes, run tests"
- "Skip the test, I'll manually verify"
- "It's probably X, let me fix that"
- "I don't fully understand but this might work"
- "Pattern says X but I'll adapt it differently"
- "Here are the main problems: [lists fixes without investigation]"
- Proposing solutions before tracing data flow
- "One more fix attempt" (when already tried 2+)
- Each fix reveals new problem in different place
ALL of these mean: STOP. Return to Phase 1.
If 3+ fixes failed: Question the architecture (see Phase 4.5)
your human partner's Signals You're Doing It Wrong
Watch for these redirections:
- "Is that not happening?" - You assumed without verifying
- "Will it show us...?" - You should have added evidence gathering
- "Stop guessing" - You're proposing fixes without understanding
- "Ultrathink this" - Question fundamentals, not just symptoms
- "We're stuck?" (frustrated) - Your approach isn't working
When you see these: STOP. Return to Phase 1.
Common Rationalizations
| Excuse |
Reality |
| "Issue is simple, don't need process" |
Simple issues have root causes too. Process is fast for simple bugs. |
| "Emergency, no time for process" |
Systematic debugging is FASTER than guess-and-check thrashing. |
| "Just try this first, then investigate" |
First fix sets the pattern. Do it right from the start. |
| "I'll write test after confirming fix works" |
Untested fixes don't stick. Test first proves it. |
| "Multiple fixes at once saves time" |
Can't isolate what worked. Causes new bugs. |
| "Reference too long, I'll adapt the pattern" |
Partial understanding guarantees bugs. Read it completely. |
| "I see the problem, let me fix it" |
Seeing symptoms ≠ understanding root cause. |
| "One more fix attempt" (after 2+ failures) |
3+ failures = architectural problem. Question pattern, don't fix again. |
Quick Reference
| Phase |
Key Activities |
Success Criteria |
| 1. Root Cause |
Read errors, reproduce, check changes, gather evidence |
Understand WHAT and WHY |
| 2. Pattern |
Find working examples, compare |
Identify differences |
| 3. Hypothesis |
Form theory, test minimally |
Confirmed or new hypothesis |
| 4. Implementation |
Create test, fix, verify |
Bug resolved, tests pass |
When Process Reveals "No Root Cause"
If systematic investigation reveals issue is truly environmental, timing-dependent, or external:
- You've completed the process
- Document what you investigated
- Implement appropriate handling (retry, timeout, error message)
- Add monitoring/logging for future investigation
But: 95% of "no root cause" cases are incomplete investigation.
Supporting Techniques
These techniques are part of systematic debugging and available in this directory:
root-cause-tracing.md - Trace bugs backward through call stack to find original trigger
defense-in-depth.md - Add validation at multiple layers after finding root cause
condition-based-waiting.md - Replace arbitrary timeouts with condition polling
Related skills:
- superpowers:test-driven-development - For creating failing test case (Phase 4, Step 1)
- superpowers:verification-before-completion - Verify fix worked before claiming success
Real-World Impact
From debugging sessions:
- Systematic approach: 15-30 minutes to fix
- Random fixes approach: 2-3 hours of thrashing
- First-time fix rate: 95% vs 40%
- New bugs introduced: Near zero vs common
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: systematic-debugging3description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes4metadata:5 source: https://skillmd.com/skills/iradoweck/systematic-debugging6 aas-risk: critical7 aas-source: community8 aas-date-added: '2026-02-27'9---1011# Systematic Debugging1213## Overview1415Random fixes waste time and create new bugs. Quick patches mask underlying issues.1617**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.1819**Violating the letter of this process is violating the spirit of debugging.**2021## The Iron Law2223```24NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST25```2627If you haven't completed Phase 1, you cannot propose fixes.2829## When to Use30Use for ANY technical issue:31- Test failures32- Bugs in production33- Unexpected behavior34- Performance problems35- Build failures36- Integration issues3738**Use this ESPECIALLY when:**39- Under time pressure (emergencies make guessing tempting)40- "Just one quick fix" seems obvious41- You've already tried multiple fixes42- Previous fix didn't work43- You don't fully understand the issue4445**Don't skip when:**46- Issue seems simple (simple bugs have root causes too)47- You're in a hurry (rushing guarantees rework)48- Manager wants it fixed NOW (systematic is faster than thrashing)4950## The Four Phases5152You MUST complete each phase before proceeding to the next.5354### Phase 1: Root Cause Investigation5556**BEFORE attempting ANY fix:**57581. **Read Error Messages Carefully**59 - Don't skip past errors or warnings60 - They often contain the exact solution61 - Read stack traces completely62 - Note line numbers, file paths, error codes63642. **Reproduce Consistently**65 - Can you trigger it reliably?66 - What are the exact steps?67 - Does it happen every time?68 - If not reproducible → gather more data, don't guess69703. **Check Recent Changes**71 - What changed that could cause this?72 - Git diff, recent commits73 - New dependencies, config changes74 - Environmental differences75764. **Gather Evidence in Multi-Component Systems**7778 **WHEN system has multiple components (CI → build → signing, API → service → database):**7980 **BEFORE proposing fixes, add diagnostic instrumentation:**81 ```82 For EACH component boundary:83 - Log what data enters component84 - Log what data exits component85 - Verify environment/config propagation86 - Check state at each layer8788 Run once to gather evidence showing WHERE it breaks89 THEN analyze evidence to identify failing component90 THEN investigate that specific component91 ```9293 **Example (multi-layer system):**94 ```bash95 # Layer 1: Workflow96 echo "=== Secrets available in workflow: ==="97 echo "IDENTITY: ${IDENTITY:+SET}${IDENTITY:-UNSET}"9899 # Layer 2: Build script100 echo "=== Env vars in build script: ==="101 env | grep IDENTITY || echo "IDENTITY not in environment"102103 # Layer 3: Signing script104 echo "=== Keychain state: ==="105 security list-keychains106 security find-identity -v107108 # Layer 4: Actual signing109 codesign --sign "$IDENTITY" --verbose=4 "$APP"110 ```111112 **This reveals:** Which layer fails (secrets → workflow ✓, workflow → build ✗)1131145. **Trace Data Flow**115116 **WHEN error is deep in call stack:**117118 See `root-cause-tracing.md` in this directory for the complete backward tracing technique.119120 **Quick version:**121 - Where does bad value originate?122 - What called this with bad value?123 - Keep tracing up until you find the source124 - Fix at source, not at symptom125126### Phase 2: Pattern Analysis127128**Find the pattern before fixing:**1291301. **Find Working Examples**131 - Locate similar working code in same codebase132 - What works that's similar to what's broken?1331342. **Compare Against References**135 - If implementing pattern, read reference implementation COMPLETELY136 - Don't skim - read every line137 - Understand the pattern fully before applying1381393. **Identify Differences**140 - What's different between working and broken?141 - List every difference, however small142 - Don't assume "that can't matter"1431444. **Understand Dependencies**145 - What other components does this need?146 - What settings, config, environment?147 - What assumptions does it make?148149### Phase 3: Hypothesis and Testing150151**Scientific method:**1521531. **Form Single Hypothesis**154 - State clearly: "I think X is the root cause because Y"155 - Write it down156 - Be specific, not vague1571582. **Test Minimally**159 - Make the SMALLEST possible change to test hypothesis160 - One variable at a time161 - Don't fix multiple things at once1621633. **Verify Before Continuing**164 - Did it work? Yes → Phase 4165 - Didn't work? Form NEW hypothesis166 - DON'T add more fixes on top1671684. **When You Don't Know**169 - Say "I don't understand X"170 - Don't pretend to know171 - Ask for help172 - Research more173174### Phase 4: Implementation175176**Fix the root cause, not the symptom:**1771781. **Create Failing Test Case**179 - Simplest possible reproduction180 - Automated test if possible181 - One-off test script if no framework182 - MUST have before fixing183 - Use the `superpowers:test-driven-development` skill for writing proper failing tests1841852. **Implement Single Fix**186 - Address the root cause identified187 - ONE change at a time188 - No "while I'm here" improvements189 - No bundled refactoring1901913. **Verify Fix**192 - Test passes now?193 - No other tests broken?194 - Issue actually resolved?1951964. **If Fix Doesn't Work**197 - STOP198 - Count: How many fixes have you tried?199 - If < 3: Return to Phase 1, re-analyze with new information200 - **If ≥ 3: STOP and question the architecture (step 5 below)**201 - DON'T attempt Fix #4 without architectural discussion2022035. **If 3+ Fixes Failed: Question Architecture**204205 **Pattern indicating architectural problem:**206 - Each fix reveals new shared state/coupling/problem in different place207 - Fixes require "massive refactoring" to implement208 - Each fix creates new symptoms elsewhere209210 **STOP and question fundamentals:**211 - Is this pattern fundamentally sound?212 - Are we "sticking with it through sheer inertia"?213 - Should we refactor architecture vs. continue fixing symptoms?214215 **Discuss with your human partner before attempting more fixes**216217 This is NOT a failed hypothesis - this is a wrong architecture.218219## Red Flags - STOP and Follow Process220221If you catch yourself thinking:222- "Quick fix for now, investigate later"223- "Just try changing X and see if it works"224- "Add multiple changes, run tests"225- "Skip the test, I'll manually verify"226- "It's probably X, let me fix that"227- "I don't fully understand but this might work"228- "Pattern says X but I'll adapt it differently"229- "Here are the main problems: [lists fixes without investigation]"230- Proposing solutions before tracing data flow231- **"One more fix attempt" (when already tried 2+)**232- **Each fix reveals new problem in different place**233234**ALL of these mean: STOP. Return to Phase 1.**235236**If 3+ fixes failed:** Question the architecture (see Phase 4.5)237238## your human partner's Signals You're Doing It Wrong239240**Watch for these redirections:**241- "Is that not happening?" - You assumed without verifying242- "Will it show us...?" - You should have added evidence gathering243- "Stop guessing" - You're proposing fixes without understanding244- "Ultrathink this" - Question fundamentals, not just symptoms245- "We're stuck?" (frustrated) - Your approach isn't working246247**When you see these:** STOP. Return to Phase 1.248249## Common Rationalizations250251| Excuse | Reality |252|--------|---------|253| "Issue is simple, don't need process" | Simple issues have root causes too. Process is fast for simple bugs. |254| "Emergency, no time for process" | Systematic debugging is FASTER than guess-and-check thrashing. |255| "Just try this first, then investigate" | First fix sets the pattern. Do it right from the start. |256| "I'll write test after confirming fix works" | Untested fixes don't stick. Test first proves it. |257| "Multiple fixes at once saves time" | Can't isolate what worked. Causes new bugs. |258| "Reference too long, I'll adapt the pattern" | Partial understanding guarantees bugs. Read it completely. |259| "I see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. |260| "One more fix attempt" (after 2+ failures) | 3+ failures = architectural problem. Question pattern, don't fix again. |261262## Quick Reference263264| Phase | Key Activities | Success Criteria |265|-------|---------------|------------------|266| **1. Root Cause** | Read errors, reproduce, check changes, gather evidence | Understand WHAT and WHY |267| **2. Pattern** | Find working examples, compare | Identify differences |268| **3. Hypothesis** | Form theory, test minimally | Confirmed or new hypothesis |269| **4. Implementation** | Create test, fix, verify | Bug resolved, tests pass |270271## When Process Reveals "No Root Cause"272273If systematic investigation reveals issue is truly environmental, timing-dependent, or external:2742751. You've completed the process2762. Document what you investigated2773. Implement appropriate handling (retry, timeout, error message)2784. Add monitoring/logging for future investigation279280**But:** 95% of "no root cause" cases are incomplete investigation.281282## Supporting Techniques283284These techniques are part of systematic debugging and available in this directory:285286- **`root-cause-tracing.md`** - Trace bugs backward through call stack to find original trigger287- **`defense-in-depth.md`** - Add validation at multiple layers after finding root cause288- **`condition-based-waiting.md`** - Replace arbitrary timeouts with condition polling289290**Related skills:**291- **superpowers:test-driven-development** - For creating failing test case (Phase 4, Step 1)292- **superpowers:verification-before-completion** - Verify fix worked before claiming success293294## Real-World Impact295296From debugging sessions:297- Systematic approach: 15-30 minutes to fix298- Random fixes approach: 2-3 hours of thrashing299- First-time fix rate: 95% vs 40%300- New bugs introduced: Near zero vs common301302## Limitations303- Use this skill only when the task clearly matches the scope described above.304- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.305- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.