debug

Run a fixed eight-step debugging pipeline for bug diagnosis and resolution.

Updated Apr 13, 2026

Search Tags:#debugging #traceability #bug-tracking #structured-workflow #spec-check #debug-logs

Ready to run

npx skills add https://github.com/GarethJB/workflow-plugin --skill debug-garethjb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/GarethJB/workflow-plugin/tree/main/skills/debug
Command: npx skills add https://github.com/GarethJB/workflow-plugin --skill debug-garethjb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging is often ad hoc, error-prone, and hard to reproduce. This skill enforces a fixed eight-step pipeline to ensure consistent problem diagnosis, thorough verification, and reliable resolution.

Core Features & Use Cases

Fixed eight-step debugging pipeline: symptoms capture, spec check, hypothesis, verification, root cause, fix, regression test, and completion.
Structured debugging records in debug-logs with status, related_spec, triggering_ac, and changelog integration to preserve traceability.
Spec discrepancy flagging and traceability to guide spec writers and development teams when misalignment is found.

Quick Start

Initiate the eight-step debug pipeline on a reported issue and record symptoms in the debug-logs folder to begin structured diagnosis.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I structure a debugging workflow for reproduce-at-will bugs?▼

To structure a debugging workflow for reproduce-at-will bugs, apply a fixed eight-step pipeline: symptom capture, spec check, hypothesis, verification, root cause, fix, regression test, and completion. This enforces consistent diagnosis and thorough verification.

What is a structured bug-fixing pipeline and when do I need it?▼

A structured bug-fixing pipeline is a standardized process ensuring consistent problem diagnosis and thorough verification. You need it when tackling crashes, performance issues, or reproduce-at-will bugs to prevent ad hoc, error-prone debugging.

How do I maintain traceability during bug tracking?▼

To maintain traceability during bug tracking, record structured debugging entries in debug-logs capturing status, related_spec, triggering_ac, and changelog integration. This preserves traceability and records speculation and verification outcomes throughout resolution.

Does this structured debugging approach work for spec discrepancies?▼

Yes, this structured debugging approach works for spec discrepancies by flagging misalignments during the spec check step. It guides spec writers and development teams by maintaining spec integrity and tracing issues back to related specifications.

What's the best way to verify a root cause during bug diagnosis?▼

The best way to verify a root cause during bug diagnosis is through a fixed pipeline requiring hypothesis generation and verification before applying a fix. This ensures thorough verification and records outcomes for traceability.

Why do I need a regression test step in my debugging workflow?▼

You need a regression test step in your debugging workflow to ensure reliable resolution and prevent recurring issues. It acts as the seventh step in the pipeline, verifying the fix before completion and recording the outcome in debug-logs.