gsd-debuglisted

<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 chec