skills.rest
pradeepmouli
pradeepmouliCOMMUNITY
Explore all skills by this author →
GitHub

speckit-superb-debug

Coordinates a four-phase root-cause debugging workflow with TDD gate integration.

2|Updated Jan 29, 2026
Search Tags:#tdd#debugging#evidence#escalation#root-cause#hypothesis-testing
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-superb-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-superb-debug
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-superb-debug
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-superb-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined, root-cause-first debugging protocol to fix blockers before attempting changes, reducing wasted fixes and blind patches.

Core Features & Use Cases

  • Phase-based debugging: evidence gathering, pattern analysis, one-hypothesis testing, and controlled implementation.
  • Escalation rules: stop after 3 failed fixes and propose architectural reconsideration when needed.
  • TDD-gate integration: acts as an escalation path from TDD cycles to resolve deeply blocked tasks.

Quick Start

Follow the four-phase protocol to reproduce issues, gather evidence, analyze differences, form a single hypothesis, and implement a minimal fix.

Frequently Asked Questions about speckit-superb-debug

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

FAQPage Schema
What is root-cause debugging and when should I use it instead of applying quick patches?▼

Root-cause debugging is a disciplined protocol that identifies the fundamental cause of blockers before attempting fixes. Use it when quick patches fail, fixes stall, or you need to stop wasting effort on blind patches during complex bug investigations.

How do I debug a stalled fix using a structured root-cause workflow?▼

To debug a stalled fix, follow a four-phase workflow: gather evidence by reproducing the issue, analyze patterns, test a single hypothesis, and implement a controlled minimal fix to resolve the blocker systematically.

Can I integrate root-cause debugging with my existing TDD cycles?▼

Yes, root-cause debugging integrates directly with TDD cycles by acting as an escalation path. When TDD tasks become deeply blocked, the protocol enforces evidence collection and hypothesis testing to unblock the cycle.

When should I escalate a bug investigation and reconsider the architecture?▼

You should escalate a bug investigation after 3 failed fixes. The protocol enforces an escalation rule to stop attempting patches and propose architectural reconsideration to prevent wasted effort.

What's the best way to test a debugging hypothesis without introducing new bugs?▼

The best way to test a debugging hypothesis is through controlled implementation. Form a single hypothesis based on evidence and pattern analysis, then apply a minimal fix to verify the root-cause without introducing regressions.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
carlosamesarcarlosamesar
1

gd-debugger

Diagnoses software bugs and verifies minimal code changes with regression tests.

Community
Advanced
alunadevalunadev
3

systematic-debugging

Enforces evidence-based debugging protocol to confirm root causes before code changes.

Community
Advanced
Busboom-FooBusboom-Foo

systematic-debugging

Executes a four-phase debugging workflow with evidence gathering and hypothesis testing.

Official
Advanced