Skill Tracer
Skills › Superpowers › systematic-debugging › CREATION-LOG.md

CREATION-LOG.md

119 lines · skills/systematic-debugging/CREATION-LOG.md at 2ce8aa1

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Creation Log: Systematic Debugging Skill
2
3Reference example of extracting, structuring, and bulletproofing a critical skill.
4

Creation Log: Systematic Debugging Skill

Reference example of extracting, structuring, and bulletproofing a critical skill.

Raw lines 1 to 4
5## Source Material
6
7Extracted debugging framework from `~/.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

Source Material

Extracted debugging framework from ~/.claude/CLAUDE.md:

  • 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation)
  • Core mandate: ALWAYS find root cause, NEVER fix symptoms
  • Rules designed to resist time pressure and rationalization
Raw lines 5 to 11
Project instruction file CLAUDE.md :7
12## Extraction Decisions
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
20**What to leave out:**
21- Project-specific context
22- Repetitive variations of same rule
23- Narrative explanations (condensed to principles)

Extraction Decisions

What to include:

  • Complete 4-phase framework with all rules
  • Anti-shortcuts ("NEVER fix symptom", "STOP and re-analyze")
  • Pressure-resistant language ("even if faster", "even if I seem in a hurry")
  • Concrete steps for each phase

What to leave out:

  • Project-specific context
  • Repetitive variations of same rule
  • Narrative explanations (condensed to principles)
Raw lines 12 to 24
25## Structure Following skill-creation/SKILL.md
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)

Structure Following skill-creation/SKILL.md

  1. Rich when_to_use - Included symptoms and anti-patterns
  2. Type: technique - Concrete process with steps
  3. Keywords - "root cause", "symptom", "workaround", "debugging", "investigation"
  4. Flowchart - Decision point for "fix failed" → re-analyze vs add more fixes
  5. Phase-by-phase breakdown - Scannable checklist format
  6. Anti-patterns section - What NOT to do (critical for this skill)
Raw lines 25 to 33
34## Bulletproofing Elements
36Framework designed to resist rationalization under pressure:

Bulletproofing Elements

Framework designed to resist rationalization under pressure:

Raw lines 34 to 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)

Language Choices

  • "ALWAYS" / "NEVER" (not "should" / "try to")
  • "even if faster" / "even if I seem in a hurry"
  • "STOP and re-analyze" (explicit pause)
  • "Don't skip past" (catches the actual behavior)
Raw lines 38 to 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

Structural Defenses

  • Phase 1 required - Can't skip to implementation
  • Single hypothesis rule - Forces thinking, prevents shotgun fixes
  • Explicit failure mode - "IF your first fix doesn't work" with mandatory action
  • Anti-patterns section - Shows exactly what shortcuts look like
Raw lines 44 to 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

Redundancy

  • Root cause mandate in overview + when_to_use + Phase 1 + implementation rules
  • "NEVER fix symptom" appears 4 times in different contexts
  • Each phase has explicit "don't skip" guidance
Raw lines 50 to 54
55## Testing Approach
57Created 4 validation tests following skills/meta/testing-skills-with-subagents:

Testing Approach

Created 4 validation tests following skills/meta/testing-skills-with-subagents:

Raw lines 55 to 58
Starts an agent subagents :57
59### Test 1: Academic Context (No Pressure)
60- Simple bug, no time pressure
61- **Result:** Perfect compliance, complete investigation

Test 1: Academic Context (No Pressure)

  • Simple bug, no time pressure
  • Result: Perfect compliance, complete investigation
Raw lines 59 to 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

Test 2: Time Pressure + Obvious Quick Fix

  • User "in a hurry", symptom fix looks easy
  • Result: Resisted shortcut, followed full process, found real root cause
Raw lines 63 to 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

Test 3: Complex System + Uncertainty

  • Multi-layer failure, unclear if can find root cause
  • Result: Systematic investigation, traced through all layers, found source
Raw lines 67 to 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)
75**All tests passed.** No rationalizations found.

Test 4: Failed First Fix

  • Hypothesis doesn't work, temptation to add more fixes
  • Result: Stopped, re-analyzed, formed new hypothesis (no shotgun)

All tests passed. No rationalizations found.

Raw lines 71 to 76
77## Iterations

Iterations

Raw lines 77 to 78
79### Initial Version
80- Complete 4-phase framework
81- Anti-patterns section
82- Flowchart for "fix failed" decision

Initial Version

  • Complete 4-phase framework
  • Anti-patterns section
  • Flowchart for "fix failed" decision
Raw lines 79 to 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

Enhancement 1: TDD Reference

  • Added link to skills/testing/test-driven-development
  • Note explaining TDD's "simplest code" ≠ debugging's "root cause"
  • Prevents confusion between methodologies
Raw lines 84 to 88
89## Final Outcome
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

Final Outcome

Bulletproof skill that:

  • ✅ Clearly mandates root cause investigation
  • ✅ Resists time pressure rationalization
  • ✅ Provides concrete steps for each phase
  • ✅ Shows anti-patterns explicitly
  • ✅ Tested under multiple pressure scenarios
  • ✅ Clarifies relationship to TDD
  • ✅ Ready for use
Raw lines 89 to 99
100## Key Insight
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.

Key Insight

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.

Raw lines 100 to 103
104## Usage Example
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
113**Time investment:** 5-10 minutes
114**Time saved:** Hours of symptom-whack-a-mole
116---
118*Created: 2025-10-03*
119*Purpose: Reference example for skill extraction and bulletproofing*

Usage Example

When encountering a bug:

  1. Load skill: skills/debugging/systematic-debugging
  2. Read overview (10 sec) - reminded of mandate
  3. Follow Phase 1 checklist - forced investigation
  4. If tempted to skip - see anti-pattern, stop
  5. Complete all phases - root cause found

Time investment: 5-10 minutes Time saved: Hours of symptom-whack-a-mole

Created: 2025-10-03 Purpose: Reference example for skill extraction and bulletproofing

Raw lines 104 to 119