gsd-debug

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

Updated Feb 11, 2026

Search Tags:#debugging #root cause analysis #checkpointing #issue triage #persistent state #subagent orchestration

Ready to run

npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-debug-artriv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-debug
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-debug-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically debug complex issues by capturing symptoms, preserving investigation context across context resets, and guiding an isolated subagent to reach a root cause and actionable next steps.

Core Features & Use Cases

Persistent session-aware debugging: Checks for active debug sessions in the planning workspace and resumes when appropriate.
Scientific-method symptom gathering: Collects expected vs. actual behavior, errors, timeline, and reproduction steps via user prompts.
Subagent-based investigation workflow: Spawns a dedicated gsd-debugger subagent, handles checkpoints, and continues from saved debug files until the root cause is confirmed.

Quick Start

Tell the skill what is happening (include expected behavior, actual behavior, and any error messages) so it can start a new investigation or resume an existing one.

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 without losing context after a session reset?▼

Debug complex software issues by gathering symptoms and running a structured investigation to identify root causes. It supports bug triage, reproduction debugging, and stepwise remediation where context can reset between attempts.

What is the best way to systematically triage bugs and find root causes?▼

Systematic bug triage uses a scientific-method approach to collect expected versus actual behavior, errors, timelines, and reproduction steps. An isolated subagent then executes a structured investigation workflow until the root cause is confirmed.

How do I start a root cause analysis investigation when my application throws errors?▼

To start a root cause analysis investigation, provide the expected behavior, actual behavior, and any error messages. The skill uses these symptoms to initiate a new investigation or resume an existing debug file workflow.

Can I resume a debugging session if my environment or context resets mid-investigation?▼

Yes, you can resume a debugging session because the workflow uses a persistent debug file. It checks the planning workspace for active sessions and continues from saved checkpoints without losing prior investigation context.

Does subagent orchestration help with isolating software issue reproduction steps?▼

Subagent orchestration helps isolate software issue reproduction by spawning a dedicated debugger subagent. This subagent executes investigation steps independently, handling checkpoints and continuing until the root cause is confirmed.