GSD Debugger

Organize debugging workflows with persistent state and evidence-based reasoning.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/apsulli/gmail-intel --skill gsd-debugger-apsulli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Debugger
Source: https://github.com/apsulli/gmail-intel/tree/main/.opencode/skills/debugger
Command: npx skills add https://github.com/apsulli/gmail-intel --skill gsd-debugger-apsulli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines debugging by maintaining persistent context, capturing hypotheses, and documenting evidence to prevent rework and promote root-cause isolation.

Core Features & Use Cases

  • Persistent state across debugging sessions to preserve context and hypotheses.
  • Structured hypothesis testing and evidence collection to drive faster root-cause analysis.
  • Templates for DEBUG.md and STATE.md to document progress and verification steps.
  • Guided workflows for common debugging scenarios (minimal reproduction, differential debugging, binary search).

Quick Start

Describe the bug succinctly to initiate a structured debugging session and generate a DEBUG.md with hypotheses and tests.

Frequently Asked Questions about GSD Debugger

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

FAQPage Schema
How do I maintain debugging context across multiple sessions for a complex software bug?

You can execute structured debugging workflows by documenting hypotheses and evidence in DEBUG.md and STATE.md templates, applying techniques like minimal reproduction, differential debugging, and binary search to isolate root causes.

What is the best way to track hypotheses and evidence during root-cause analysis?

Hypothesis tracking during root-cause analysis is managed through structured documentation templates that record persistent state, evidence collection, and verification steps, preventing rework and promoting disciplined, evidence-based reasoning.

Can I use this structured debugging workflow for cross-team investigations?

Yes, this structured debugging workflow supports cross-team investigations by maintaining persistent context and documenting evidence-based reasoning, ensuring all participants can track hypotheses, experiments, and verification steps consistently.

How do I start a structured debugging session to isolate a software bug?

To start a structured debugging session, describe the bug succinctly to initiate the workflow, which generates a DEBUG.md file populated with initial hypotheses, experiments, and tests for systematic root-cause tracking.

Does this debugging approach require specific file formats or templates to work?

Yes, this debugging approach requires well-defined frontmatter metadata and structured outputs such as DEBUG.md and STATE.md files to capture hypotheses, experiments, and verification steps for effective root-cause tracking.