skills.rest
abeldotam
abeldotamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

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
One-click install
npx skills add https://github.com/abeldotam/bmad-viewer --skill systematic-debugging-abeldotam
Or copy as Structured Prompt for Agent▼
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.

Related Skills

Explore More Software Engineering Skills→
rbah31rbah31
5

runbook

Investigate production symptoms and generate structured incident reports from logs, metrics, and traces.

Community
Intermediate
han-so1omonhan-so1omon
1

systematic-debugging

Identify and eliminate root-cause issues through a four-phase debugging process.

Community
Advanced
fratilanicofratilanico
7

systematic-debugging

Trace bugs to root causes through call chains and data flow.

Community
Advanced
yun520-1yun520-1
38

superpowers-systematic-debugging

Guides users through a four-phase debugging process to identify root causes of technical issues.

Community
Advanced