systematic-debugging

Identify root causes of bugs through a four-phase debugging process.

4|1|Updated Feb 3, 2026

Search Tags:#testing #debugging #defense-in-depth #tracing #root-cause #root-cause-analysis #phase-based

Ready to run

npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill systematic-debugging-lespaceman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/lespaceman/athena-workflow-marketplace/tree/main/plugins/superpowers/skills/systematic-debugging
Command: npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill systematic-debugging-lespaceman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging ensures root-cause analysis is performed before any fixes, preventing symptom-driven patches and reducing rework.

Core Features & Use Cases

Four-phase process (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation) to structure debugging.
Defense-in-depth: add validation and instrumentation across layers to catch issues early.
Safer, faster resolutions in production and CI by tracing data flow and preventing premature fixes.

Quick Start

Follow Phase 1 through Phase 4 in order to root-cause and validate every fix before deployment.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I perform root cause analysis for flaky tests and production bugs?▼

Root cause analysis for flaky tests and production bugs is performed using a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This structured approach prevents premature symptom fixes and ensures fixes target the actual root cause.

What is the best way to structure debugging for production incidents?▼

The best way to structure debugging for production incidents is a phase-based approach applying defense-in-depth and tracing. This traces data flow across layers to guarantee safer, faster resolutions by validating fixes before deployment.

Why do my bug fixes cause regressions and how can systematic debugging prevent this?▼

Bug fixes cause regressions when they address symptoms instead of root causes. Systematic debugging prevents this by enforcing root-cause investigation before implementation, adding validation and instrumentation to catch issues early and reduce rework.

How do I add defense-in-depth validation when tracing data flow during debugging?▼

Defense-in-depth validation is added during debugging by instrumenting across system layers to trace data flow. This catches issues early and validates that fixes target root causes before deployment, ensuring safer CI and production resolutions.

When should I use a phase-based debugging process instead of patching symptoms?▼

A phase-based debugging process should be used whenever addressing development tasks, production incidents, or flaky behavior scenarios. It ensures root-cause analysis is fully performed before any fixes, preventing symptom-driven patches and reducing rework.