gsd-debug

Diagnose software issues with a persistent, stateful subagent workflow.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-debug-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-debug
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-debug-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and isolates software issues using a persistent, stateful subagent workflow.

Core Features & Use Cases

  • Orchestrates a gsd-debugger subagent to diagnose issues with hypothesis-driven investigation.
  • Maintains persistent state across context resets to allow multi-step troubleshooting.
  • Handles symptom gathering, checkpoint responses, and controlled fix workflows.

Quick Start

Start a session with gsd-debug to begin diagnosing an issue using a persistent, stateful debugger.

Frequently Asked Questions about gsd-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug complex software issues iteratively across context resets?

Persistent stateful debugging tracks diagnostics across sessions using checkpoints, allowing iterative symptom gathering and controlled fixes even after context resets. It orchestrates subagents to maintain hypothesis-driven investigation state.

What is the best way to orchestrate subagents for hypothesis-driven debugging?

Subagent orchestration for debugging delegates diagnostic tasks to a dedicated subagent, managing hypothesis testing and symptom collection. The orchestrator coordinates these subagents while maintaining persistent state across the workflow.

How do I maintain debugging state across multiple sessions in Claude workflows?

Stateful debugging maintains persistent state across context resets by saving checkpoints during diagnosis. This allows multi-step troubleshooting workflows to resume with previous diagnostic data intact.

Can I use checkpoint handling to isolate software issues in automated workflows?

Checkpoint handling in automated workflows saves diagnostic progress at key stages, enabling controlled fix workflows and issue isolation. Stateful subagents process these checkpoints to track symptom gathering across sessions.

Does stateful debugging require an orchestrator to manage subagents?

Stateful debugging requires an orchestrator to coordinate subagents, handle model resolution, and manage safe checkpointing. These components work together to track diagnostics and maintain persistent state across context resets.

When should I use persistent stateful debugging instead of standard debugging?

Persistent stateful debugging suits complex issues requiring multi-step troubleshooting, iterative symptom gathering, and cross-session diagnosis. Standard debugging lacks checkpoint handling for maintaining state across context resets in automated workflows.