Systematic debugging with persistent state across context resets
$ARGUMENTS
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
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>
<available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
<execution_context> @~/.claude/gsd-core/workflows/debug.md </execution_context>
User's input: the `` blockParse subcommands and flags from the <arguments> block BEFORE the active-session check:
<arguments> block starts with "list": SUBCMD=list, no further args<arguments> block starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace)<arguments> block starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace)<arguments> block contains --diagnose: SUBCMD=debug, diagnose_only=true, strip --diagnose from descriptionCheck for active sessions (used for non-list/status/continue flows):
ls .planning/debug/*.md 2>/dev/null | grep -v '/knowledge-base\.md$' | head -5open-gsd/gsd-core
99bbbac
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.