Systematic debugging with persistent state across context resets
Scanned 9/2/2026
Install to Claude Code
npx -y skills add friday-ai-codes/friday-ai --skill gsd-debug --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Gsd Debug?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/friday-ai-codes-gsd-debug)More formats (shields.io, HTML) on the badges page.
---
name: gsd-debug
description: "Systematic debugging with persistent state across context resets"
---
<cursor_skill_adapter>
## A. Skill Invocation
- This skill is invoked when the user mentions `gsd-debug` or describes a task matching this skill.
- Treat all user text after the skill mention as `{{GSD_ARGS}}`.
- If no arguments are present, treat `{{GSD_ARGS}}` as empty.
## B. User Prompting
When the workflow needs user input, prompt the user conversationally:
- Present options as a numbered list in your response text
- Ask the user to reply with their choice
- For multi-select, ask for comma-separated numbers
## C. Tool Usage
Use these Cursor tools when executing GSD workflows:
- `Shell` for running commands (terminal operations)
- `StrReplace` for editing existing files
- `Read`, `Write`, `Glob`, `Grep`, `Task`, `WebSearch`, `WebFetch`, `TodoWrite` as needed
## D. Subagent Spawning
When the workflow needs to spawn a subagent:
- Use `Task(subagent_type="generalPurpose", ...)`
- The `model` parameter maps to Cursor's model options (e.g., "fast")
</cursor_skill_adapter>
<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>
@/Users/zaneliu/Projects/open-source/friday-ai/.cursor/gsd-core/workflows/debug.md
</execution_context>
<context>
User's input: {{GSD_ARGS}}
Parse subcommands and flags from {{GSD_ARGS}} BEFORE the active-session check:
- If {{GSD_ARGS}} starts with "list": SUBCMD=list, no further args
- If {{GSD_ARGS}} starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace)
- If {{GSD_ARGS}} starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace)
- If {{GSD_ARGS}} 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>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!