spectra-debug

Debug bugs with a four-phase Reproduce, Isolate, Root Cause, Fix workflow.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-debug-ycs77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-debug
Source: https://github.com/ycs77/gh-aw-todo-app/tree/main/.claude/skills/spectra-debug
Command: npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-debug-ycs77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically debug problems using a disciplined, four-phase workflow to eliminate guesswork and track evidence.

Core Features & Use Cases

  • Enforces a four-phase debugging process: Reproduce, Isolate, Root Cause, Fix.
  • Provides clear guardrails and a documented approach to avoid symptomatic fixes.
  • Useful for debugging regressions, flaky tests, and behavior changes across projects.

Quick Start

Reproduce the bug, then apply the four-phase workflow to identify and fix the root cause.

Frequently Asked Questions about spectra-debug

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

FAQPage Schema
What is a systematic debugging workflow for isolating a root cause?

A systematic debugging workflow enforces a four-phase process: Reproduce, Isolate, Root Cause, and Fix. This structured approach eliminates guesswork, tracks evidence, and prevents symptomatic fixes when resolving software bugs and behavior regressions.

How do I fix flaky tests and behavior regressions without guesswork?

To fix flaky tests and behavior regressions without guesswork, apply a disciplined four-phase workflow: first reproduce the bug, then isolate the variables, identify the root cause, and finally apply the targeted fix with proper documentation.

What's the best way to triage bugs across a complex codebase?

The best way to triage bugs across a complex codebase is to follow a structured four-phase process—Reproduce, Isolate, Root Cause, Fix—which provides clear guardrails and documentation prompts to systematically resolve behavior changes.

How can I reproduce a bug before attempting a code fix?

To reproduce a bug before attempting a fix, you must consistently trigger the error condition as the first phase of the debugging workflow, establishing a reliable baseline before moving forward to isolate variables and locate the root cause.

When should I stop attempting fixes and reconsider my root cause analysis?

You should stop attempting fixes and reconsider your root cause analysis after three failed attempts, as an explicit three-attempt rule prevents you from repeatedly applying ineffective symptomatic fixes instead of isolating the true underlying issue.