systematic-debugging

Trace bugs and failures to root causes through a four-phase investigation.

1|Updated Apr 5, 2026

Search Tags:#testing #debugging #defense-in-depth #systematic #hypothesis #root-cause

Ready to run

npx skills add https://github.com/mortenbroesby/playground --skill systematic-debugging-mortenbroesby

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. This skill enforces a four-phase investigative process to ensure root-cause diagnosis before fixes.

Core Features & Use Cases

Four-phase systematic debugging workflow that guides investigation from root cause to implementation.
Defense-in-depth approach: validate data across multiple layers and maintain anti-patterns to avoid shortcuts.
Applicable to bugs, test failures, production incidents, flaky tests, and complex multi-component scenarios.

Quick Start

Follow Phase 1 to begin root-cause investigation before proposing any fixes, then progress through Phases 2–4 as needed.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and when should I use it for root-cause analysis?▼

Systematic debugging is a structured four-phase investigative process that traces bugs, test failures, and unexpected behavior to root causes. Use it for production incidents, flaky tests, and multi-component scenarios before proposing any fixes.

How do I debug flaky test failures and production incidents step by step?▼

Debug flaky failures and incidents through a four-phase workflow: start with initial investigation, perform pattern analysis, conduct hypothesis testing, then implement fixes with defense-in-depth validation across multiple layers to ensure root-cause diagnosis.

Does a hypothesis-driven debugging approach work for multi-component systems?▼

Yes, hypothesis-driven debugging works for multi-component systems by enforcing pattern analysis and hypothesis testing before fixes. It applies defense-in-depth validation across multiple layers to ensure accurate root-cause diagnosis even under time pressure.

What's the best way to stop random fixes from creating new bugs during investigation?▼

Stop random fixes from creating new bugs by enforcing a four-phase investigation with explicit stop rules and anti-patterns. This mandates root-cause diagnosis and defense-in-depth validation across layers before any implementation begins.

What are the limitations of defense-in-depth debugging during production incidents?▼

The main limitation of defense-in-depth debugging during production incidents is the time required to validate data across multiple layers and test hypotheses. Strict adherence to explicit stop rules and anti-patterns may conflict with extreme time pressure.