systematic-debugging

Guide root-cause-first debugging through four phases and defense-in-depth checks.

13|Updated Feb 4, 2026

Search Tags:#debugging #investigation #defense-in-depth #tracing #hypothesis #root-cause #phase-based

Ready to run

npx skills add https://github.com/abeldotam/bmad-viewer --skill systematic-debugging-abeldotam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/abeldotam/bmad-viewer/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/abeldotam/bmad-viewer --skill systematic-debugging-abeldotam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps teams find the true root cause of bugs and production issues, preventing symptom-focused fixes.

Core Features & Use Cases

Four-phase workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) for rigorous debugging.
Defense-in-depth approach: validates data at multiple layers and traces data flow to defeat superficial fixes.
Real-world applicability: reduces mean time to resolution and improves fix quality across tests, CI, and production.

Quick Start

Follow the four-phase process to root-cause a failing issue before attempting any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is root-cause debugging and how does it fix software failures?▼

Root-cause debugging identifies the true origin of software failures by tracing data flow and validating multiple layers, ensuring fixes address the underlying issue rather than just treating symptoms.

How do I debug a production incident without applying superficial fixes?▼

Debug production incidents by enforcing a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This defense-in-depth approach validates data across layers to prevent superficial fixes.

What is the best way to investigate test failures and behavior anomalies?▼

The best way to investigate test failures and behavior anomalies is using a phase-based debugging workflow that requires strict phase completion, traces data flow, and validates hypotheses before implementing fixes.

Does systematic debugging work for both CI test failures and production issues?▼

Yes, systematic debugging applies across test failures, CI pipelines, and production incidents. It reduces mean time to resolution by enforcing root-cause-first investigation and defense-in-depth checks across all environments.

How do I validate a debugging hypothesis before implementing a fix?▼

Validate a debugging hypothesis by completing the strict Root Cause Investigation and Pattern Analysis phases first. This traces data flow and applies defense-in-depth checks to confirm the hypothesis addresses the true root cause.