skills.rest
hq-opensource
hq-opensourceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gsd-debug

Document software bug investigations in .planning/debug/{issue-id}.md files.

7|2|Updated Jun 30, 2025
Search Tags:#templates#debugging#state-management#reproducibility#root-cause-analysis
One-click install
npx skills add https://github.com/hq-opensource/predictive-control --skill gsd-debug-hq-opensource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-debug
Source: https://github.com/hq-opensource/predictive-control/tree/main/.agent/skills/gsd-debug
Command: npx skills add https://github.com/hq-opensource/predictive-control --skill gsd-debug-hq-opensource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with a persistent debug brain that survives context resets and preserves investigation progress across sessions.

Core Features & Use Cases

  • Structured debugging workflow: observe, hypothesize, experiment, and verify using dedicated files and templates.
  • Reproducible sessions: maintain continuity via .planning/debug/{issue-id}.md and standardized agent prompts.
  • Extensible tooling: leverages subagents and templates to document symptoms, evidence, root causes, and fixes for software bugs.

Quick Start

Start a debugging session by spawning the gsd-debugger with an issue overview and creating a .planning/debug/{issue-id}.md to record observations.

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 state and session continuity across context resets?▼

To maintain debugging state across context resets, document symptoms, hypotheses, experiments, and root causes in a persistent `.planning/debug/{issue-id}.md` file. This dedicated debugging brain preserves investigation progress reliably across resets.

What is the best way to perform systematic root-cause analysis for software bugs?▼

Systematic root-cause analysis involves a structured workflow: observe symptoms, hypothesize causes, experiment to gather evidence, and verify fixes. Documenting each step in standardized templates ensures reproducible investigations and reliable software bug resolution.

How do I document and reproduce a software bug investigation workflow?▼

Document a bug investigation by recording observations, evidence, root causes, and fixes in a dedicated `.planning/debug/{issue-id}.md` file using provided templates. This creates reproducible debug sessions with continuity for verification.

Does this debugging approach require any specific dependencies or subagents?▼

No specific dependencies are required to start debugging. The workflow leverages extensible tooling like subagents and standardized templates to document symptoms, evidence, root causes, and fixes for software bugs.

Can I use this systematic debugging workflow for verifying reproducible tests?▼

Yes, this workflow targets reproducible tests and verification workflows. By documenting symptoms, experiments, root causes, and fixes in structured templates, you ensure tests are reproducible and fixes are reliably verified.

Why does my debugging session lose progress when the context resets?▼

Debugging sessions lose progress without a persistent debug brain. By documenting investigations in a `.planning/debug/{issue-id}.md` file, you preserve symptoms, hypotheses, and root causes, ensuring session continuity across resets.

Related Skills

Explore More Software Engineering Skills→
jinglemansweepjinglemansweep

jp-setup

Create a .plans directory with a .gitkeep file at the repository root.

Community
Basic
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
BoxLogoDevBoxLogoDev
16

sap-session

Orchestrate multi-turn SAP diagnosis workflows across modules without live system access.

Community
Advanced
dobrinz123dobrinz123

gsd-debug

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

Community
Advanced