gsd-debug

Orchestrate persistent-context debugging with a gsd-debugger subagent.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-debug-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-debug
Command: npx skills add https://github.com/rkz91/coco --skill gsd-debug-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex issues often requires maintaining context across resets and coordinating multiple agents. This skill provides a structured, persistent-context debugging workflow using a dedicated gsd-debugger subagent to investigate symptoms without losing state.

Core Features & Use Cases

  • Orchestrated subagent debugging with isolated contexts to prevent context bleed.
  • Persistent session state across prompts, checkpoints, and restarts.
  • Checkpoint-driven workflow with the ability to spawn continuation agents and plan next steps.
  • Supports diagnose-only mode (via --diagnose) to identify root causes before applying fixes, or find-and-fix mode for end-to-end resolution.

Quick Start

Describe the issue you want investigated and initiate a debugging session by invoking the gsd-debug workflow with your issue description.

Frequently Asked Questions about gsd-debug

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

FAQPage Schema
How do I debug persistent state issues across context resets without losing session data?

Structured debugging uses an orchestrator to gather symptoms and spawn isolated subagents, preventing context bleed during root-cause analysis. This approach confines each investigation phase to a dedicated context, avoiding interference and ensuring accurate symptom tracking.

What is the best way to isolate root-cause analysis when debugging complex orchestration workflows?

Checkpointing in debugging allows you to save session state at specific investigation milestones, enabling you to spawn continuation agents and plan next steps. This checkpoint-driven workflow ensures progress is preserved across context resets, so debugging can resume seamlessly.

Can I run a debugging session in diagnose-only mode before applying any fixes?

To start an orchestrated debugging session, describe the issue you want investigated and invoke the debug workflow with your issue description. The orchestrator will automatically gather symptoms, handle checkpoints, and manage subagent isolation to investigate the problem.

How do checkpoints work when debugging issues with subagent isolation?

Find-and-fix mode provides end-to-end resolution by gathering symptoms, isolating the investigation with subagents, and directly applying fixes. Alternatively, diagnose-only mode uses the --diagnose flag to identify root causes and plan fixes without modifying the system.