1# Creation Log: Systematic Debugging Skill
2 
3Reference example of extracting, structuring, and bulletproofing a critical skill.
4 
5## Source Material
6 
7Extracted debugging framework from `/Users/jesse/.claude/CLAUDE.md`:
8- 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation)
9- Core mandate: ALWAYS find root cause, NEVER fix symptoms
10- Rules designed to resist time pressure and rationalization
11 
12## Extraction Decisions
13 
14**What to include:**
15- Complete 4-phase framework with all rules
16- Anti-shortcuts ("NEVER fix symptom", "STOP and re-analyze")
17- Pressure-resistant language ("even if faster", "even if I seem in a hurry")
18- Concrete steps for each phase
19 
20**What to leave out:**
21- Project-specific context
22- Repetitive variations of same rule
23- Narrative explanations (condensed to principles)
24 
25## Structure Following skill-creation/SKILL.md
26 
271. **Rich when_to_use** - Included symptoms and anti-patterns
282. **Type: technique** - Concrete process with steps
293. **Keywords** - "root cause", "symptom", "workaround", "debugging", "investigation"
304. **Flowchart** - Decision point for "fix failed" → re-analyze vs add more fixes
315. **Phase-by-phase breakdown** - Scannable checklist format
326. **Anti-patterns section** - What NOT to do (critical for this skill)
33 
34## Bulletproofing Elements
35 
36Framework designed to resist rationalization under pressure:
37 
38### Language Choices
39- "ALWAYS" / "NEVER" (not "should" / "try to")
40- "even if faster" / "even if I seem in a hurry"
41- "STOP and re-analyze" (explicit pause)
42- "Don't skip past" (catches the actual behavior)
43 
44### Structural Defenses
45- **Phase 1 required** - Can't skip to implementation
46- **Single hypothesis rule** - Forces thinking, prevents shotgun fixes
47- **Explicit failure mode** - "IF your first fix doesn't work" with mandatory action
48- **Anti-patterns section** - Shows exactly what shortcuts look like
49 
50### Redundancy
51- Root cause mandate in overview + when_to_use + Phase 1 + implementation rules
52- "NEVER fix symptom" appears 4 times in different contexts
53- Each phase has explicit "don't skip" guidance
54 
55## Testing Approach
56 
57Created 4 validation tests following skills/meta/testing-skills-with-subagents:
58 
59### Test 1: Academic Context (No Pressure)
60- Simple bug, no time pressure
61- **Result:** Perfect compliance, complete investigation
62 
63### Test 2: Time Pressure + Obvious Quick Fix
64- User "in a hurry", symptom fix looks easy
65- **Result:** Resisted shortcut, followed full process, found real root cause
66 
67### Test 3: Complex System + Uncertainty
68- Multi-layer failure, unclear if can find root cause
69- **Result:** Systematic investigation, traced through all layers, found source
70 
71### Test 4: Failed First Fix
72- Hypothesis doesn't work, temptation to add more fixes
73- **Result:** Stopped, re-analyzed, formed new hypothesis (no shotgun)
74 
75**All tests passed.** No rationalizations found.
76 
77## Iterations
78 
79### Initial Version
80- Complete 4-phase framework
81- Anti-patterns section
82- Flowchart for "fix failed" decision
83 
84### Enhancement 1: TDD Reference
85- Added link to skills/testing/test-driven-development
86- Note explaining TDD's "simplest code" ≠ debugging's "root cause"
87- Prevents confusion between methodologies
88 
89## Final Outcome
90 
91Bulletproof skill that:
92- ✅ Clearly mandates root cause investigation
93- ✅ Resists time pressure rationalization
94- ✅ Provides concrete steps for each phase
95- ✅ Shows anti-patterns explicitly
96- ✅ Tested under multiple pressure scenarios
97- ✅ Clarifies relationship to TDD
98- ✅ Ready for use
99 
100## Key Insight
101 
102**Most important bulletproofing:** Anti-patterns section showing exact shortcuts that feel justified in the moment. When Claude thinks "I'll just add this one quick fix", seeing that exact pattern listed as wrong creates cognitive friction.
103 
104## Usage Example
105 
106When encountering a bug:
1071. Load skill: skills/debugging/systematic-debugging
1082. Read overview (10 sec) - reminded of mandate
1093. Follow Phase 1 checklist - forced investigation
1104. If tempted to skip - see anti-pattern, stop
1115. Complete all phases - root cause found
112 
113**Time investment:** 5-10 minutes
114**Time saved:** Hours of symptom-whack-a-mole
115 
116---
117 
118*Created: 2025-10-03*
119*Purpose: Reference example for skill extraction and bulletproofing*
120