Debug issues with persistent state
gsd:debugskillsetup L1★3,035
davepoon/buildwithclaude ↗What it does
Systematically debug issues with persistent state
Best for
Investigating bugs that require multiple test cycles and evidence accumulation, when you want the investigation context isolated from main work.
Inputs
- · issue description | --diagnose flag
- · subcommands: list|status|continue
Outputs
- · .planning/debug/*.md session files
- · Root Cause Report (--diagnose mode)
- · checkpoint-resumed sessions
Requires
- · Read
- · Bash
- · Task
- · AskUserQuestion
Preconditions
.planning/debug/ directory writable; gsd-sdk available for state queries; gsd-debugger subagent model configured
Failure modes
Debug session file corrupted; slug collision with resolved sessions; subagent context timeout during deep investigation; diagnosis_only=true requested but root cause unresolved
Trust signals
- · Isolates investigation in subagent (fresh 200k context)
- · Persists sessions to .planning/debug/*.md
- · Supports continue/resume across context boundaries
- · Scientific method: hypothesis → test → evidence
- · --diagnose mode separates diagnosis from fix