msd-core/commands/gsd/debug.md at cd1bede183f635822a5f12e8657f82d58769f7d2

Files

Lex Christopherson f0b4c7d853 feat: add /gsd:debug for systematic debugging with persistent state

- Creates .planning/debug/[slug].md immediately on command
- Continuous updates: file IS the debugging brain
- Clear section rules: OVERWRITE (Current Focus, Resolution) vs APPEND (Evidence, Eliminated)
- Survives /clear perfectly - resume from any interruption point
- Scientific method: evidence → hypothesis → test → eliminate or confirm
- Includes debugging reference files (mindset, hypothesis testing, investigation techniques)

Closes #53, closes #44

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-13 11:48:14 -06:00

1.7 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd:debug

Systematic debugging with persistent state across context resets

issue description

Read

Write

Edit

Bash

Grep

Glob

AskUserQuestion

Debug issues using scientific method with a persistent debug document that survives `/clear`.

If resuming (no arguments and active session exists): pick up where you left off. If starting new: gather symptoms, then investigate autonomously.

<execution_context> @~~/.claude/get-shit-done/workflows/debug.md @~~/.claude/get-shit-done/templates/DEBUG.md </execution_context>

User's issue: $ARGUMENTS

Check for active debug sessions:

ls .planning/debug/*.md 2>/dev/null | head -5

Follow the workflow in @~/.claude/get-shit-done/workflows/debug.md

Quick reference:

Check for active sessions - Offer to resume or start new
Gather symptoms - What happened? What should happen? Errors? When?
Create DEBUG.md - Document symptoms in .planning/debug/[slug].md
Investigate - Evidence → Hypothesis → Test → Eliminate or Confirm
Fix and verify - Minimal fix, verify against original symptoms
Archive - Move to .planning/debug/resolved/

Key principle: The DEBUG.md is your memory. Update it constantly. It survives /clear.

<success_criteria>

Active sessions checked before starting new
Symptoms gathered through AskUserQuestion (not inline questions)
DEBUG.md tracks all investigation state
Scientific method followed (not random fixes)
Root cause confirmed with evidence before fixing
Fix verified and session archived </success_criteria>

1.7 KiB Raw Blame History

1.7 KiB

Raw Blame History