gsd-debug

Orchestrate multi-agent debugging with persistent state across context resets.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-debug-novatech2210-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/novatech2210-cmd/ImidusApp/tree/main/.codex/skills/gsd-debug
Command: npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-debug-novatech2210-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables systematic debugging with persistent state across context resets, helping engineers reproduce and resolve issues more efficiently.

Core Features & Use Cases

  • Maintains a persistent context across investigation steps, allowing subagents to reference prior findings without losing state.
  • Orchestrates symptom gathering, subagent debugging, and checkpoint handling to streamline complex bugs.
  • Useful for diagnosing intermittent issues that require multiple passes with preserved data.

Quick Start

Describe the issue to start a gsd-debug session, then let it gather symptoms, spawn a debugger agent, and manage checkpoints.

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 issues across context resets without losing prior diagnostic state?

Debugging across context resets requires maintaining a persistent state to preserve diagnostic data. This skill orchestrates symptom gathering and subagent collaboration, ensuring findings survive session interruptions for systematic issue resolution.

What is the best way to orchestrate subagents for a multi-step debugging workflow?

Orchestrating subagents for debugging involves spawning specialized agents to investigate specific symptoms while managing checkpoints. This consolidates results across a multi-agent workflow, allowing parallel investigation without losing track of prior diagnostic findings.

How do I diagnose intermittent bugs that require multiple diagnostic passes with preserved data?

Diagnosing intermittent bugs with preserved data involves systematically storing investigation checkpoints after each pass. This allows subagents to reference prior findings during subsequent sessions, streamlining the reproduction and resolution of complex issues.

Can I use checkpoint handling to restore a debugging session after a context reset?

Checkpoint handling enables session restoration after a context reset by maintaining persistent state across investigation steps. You can resume complex multi-agent debugging workflows directly from saved checkpoints without losing prior diagnostic data.

Does this systematic debugging approach work for diagnosing complex bugs requiring subagent collaboration?

This systematic debugging approach is designed for complex bugs requiring subagent collaboration. It orchestrates symptom gathering and result consolidation across contexts, satisfying the requirements for multi-agent workflows that demand persistent state and session restoration.