gsd-debug
open-gsd/gsd-core/skills/gsd-debug/SKILL.md
Systematic debugging with persistent state across context resets
Skill9.9k starsChanged 28 days ago
--- name: gsd-debug description: "Systematic debugging with persistent state across context resets" argument-hint: "[list | status <slug> | continue <slug> | --diagnose] [issue description]" allowed-tools: - Read - Write - Bash - Grep - Agent - AskUserQuestion --- <objective> Debug issues using scientific method with subagent isolation. **Orchestrator role:** Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations. **Flags:** - `--diagnose` — Diagnose only. Returns a Root Cause Report without applying a fix. **Subcommands:** `list` · `status <slug>` · `continue <slug>` </objective> <available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'): - gsd-debug-session-manager — manages debug checkpoint/continuation loop in isolated context - gsd-debugger — investigates bugs using scientific method </available_agent_types> <execution_context> @~/.claude/gsd-core/workflows/debug.md </execution_context> <context> User's input: $ARGUMENTS Parse subcommands and flags from $ARGUMENTS BEFORE the active-session check: - If $ARGUMENTS starts with "list": SUBCMD=list, no further args - If $ARGUMENTS starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace) - If $ARGUMENTS starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace) - If $ARGUMENTS contains `--diagnose`: SUBCMD=debug, diagnose_only=true, strip `--diagnose` from description - Otherwise: SUBCMD=debug, diagnose_only=false Check for active sessions (used for non-list/status/continue flows): ```bash ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5 ``` </context> <process> Execute end-to-end. </process>
Discussion
Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.
Posts are public.Sign in to post
No one has posted yet. Be the first.

