skills.rest
hadpadrahul
hadpadrahulCOMMUNITY
Explore all skills by this author →
GitHub

gsd-debug

Orchestrate subagents to collect symptoms and maintain debugging context across sessions.

Updated Apr 22, 2026
Search Tags:#automation#debugging#multi-agent#orchestration#root-cause#stateful-session
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-debug-hadpadrahul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-debug
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-debug-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers can systematically debug issues by preserving state across context resets, enabling faster root-cause analysis and traceability across sessions.

Core Features & Use Cases

  • Persistent debugging sessions across resets to maintain context during long investigations.
  • Orchestrator role to gather symptoms, spawn subagents (e.g., gsd-debugger), manage checkpoints, and surface concise summaries.
  • Supports commands like list, status, continue, and diagnose-only analysis to guide workflows.

Quick Start

Describe the observed issue and expected behavior to start a new, persisted debugging session.

Frequently Asked Questions about gsd-debug

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

FAQPage Schema
How do I maintain debugging context across context resets during long investigations?▼

Persistent debugging sessions maintain context across context resets by preserving investigation state, enabling you to resume long root-cause analysis workflows without losing prior findings.

Can I use multi-agent orchestration to isolate issues in complex systems?▼

Yes, multi-agent orchestration isolates issues in complex systems by spawning subagents to collect symptoms, manage checkpoints, and surface concise summaries for structured root-cause analysis.

How do I start a structured debugging session for root-cause analysis?▼

To start a structured debugging session, describe the observed issue and the expected behavior to initiate a new, persisted debugging workflow that tracks symptoms and isolates root causes.

What commands are available to guide orchestration workflows for debugging?▼

Orchestration workflows for debugging support commands like list, status, continue, and diagnose-only analysis to manage checkpoints and guide subagent task delegation safely.

Does multi-agent debugging support security-conscious task delegation?▼

Yes, multi-agent debugging supports security-conscious task delegation by implementing auditable subagent orchestration and checkpoint handling to ensure safe debugging workflows.

When should I use a stateful session for persistent investigation?▼

Use a stateful session for persistent investigation when debugging complex systems requires multi-agent collaboration, root-cause analysis, and context preservation across multiple resets.

Related Skills

Explore More Software Engineering Skills→
romiluz13romiluz13
161

debugging-patterns

Enforce root-cause investigation before applying fixes in debugging workflows.

Community
Advanced
ArtRivArtRiv

gsd-debug

Diagnose software issues by gathering symptoms and running structured root-cause investigations.

Community
Advanced
TruCol270TruCol270
1

gsd-debug

Coordinate persistent-state debugging across context resets with checkpoints.

Community
Advanced
dobrinz123dobrinz123

gsd-debug

Diagnose software issues by orchestrating symptom collection and root-cause analysis.

Community
Advanced