systematic-debugging

Investigate root causes through a four-phase debugging process.

2|Updated Jan 21, 2026

Search Tags:#debugging #defense-in-depth #traceability #phases #root-cause #software-engineering

Ready to run

npx skills add https://github.com/roderik/mpe --skill systematic-debugging-roderik

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This skill provides a disciplined, four-phase debugging framework that helps you identify root causes before proposing fixes, reducing wasteful quick patches.

## Core Features & Use Cases

Four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
Explicit gates and anti-patterns to resist time-pressure shortcuts.
Suitable for flaky tests, production incidents, and complex failure modes.

### Quick Start

Load the skill: skills/debugging/systematic-debugging
Read the overview, then execute Phase 1: Root Cause Investigation before proposing fixes
Reference related defenses: defense-in-depth and root-cause-tracing for robust debugging.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I identify a root cause before proposing software fixes?▼

Identify a root cause by executing a structured four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This enforces traceability and defense-in-depth across multiple layers to reduce wasteful quick patches.

What is the best way to debug flaky tests and production incidents?▼

Debug flaky tests and production incidents using a disciplined framework with explicit gates and anti-patterns. This structured approach resists time-pressure shortcuts, ensuring you resolve complex failure modes rather than applying superficial fixes.

How do I stop time-pressure shortcuts from causing debugging rework?▼

Stop time-pressure shortcuts by enforcing explicit gates and anti-patterns during your debugging phases. This disciplined framework resists hasty patches, reducing debugging time and rework by requiring traceability at every step.

Why should I use a systematic debugging process instead of quick patches?▼

Use a systematic debugging process instead of quick patches to eliminate wasteful rework. By enforcing pattern analysis and hypothesis testing across multiple layers, it ensures you resolve the actual source of complex failure modes.

When do I need defense-in-depth and traceability for software debugging?▼

You need defense-in-depth and traceability when resolving complex failure modes in production incidents or flaky tests. These mechanisms enforce a structured root cause investigation that stops at the source before implementation.

Can I apply systematic debugging to complex failure modes across multiple layers?▼

Yes, you can apply systematic debugging to complex failure modes across multiple layers. The framework enforces defense-in-depth and traceability, ensuring hypothesis testing and pattern analysis validate root causes before implementation.