gsd-debug

SkillDev tools

Systematic debugging with persistent state across context resets

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the gsd-debug skill

What this skill tells your AI

The instructions your AI receives, as published by protoconf/protoconf in .agents/skills/gsd-debug/SKILL.md and read by ahel’s review.

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'):

gsd-debug-session-manager — manages debug checkpoint/continuation loop in isolated context
gsd-debugger — investigates bugs using scientific method </available_agent_types>

<execution_context> @.agents/gsd-core/workflows/debug.md </execution_context>

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):

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

Advanced