systematic-debugging

Investigate technical issues through four phases to identify root causes.

Updated Jan 8, 2026

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

Ready to run

npx skills add https://github.com/jmmL/dr3-old --skill systematic-debugging-jmml

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jmmL/dr3-old/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/jmmL/dr3-old --skill systematic-debugging-jmml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to debugging that ensures you identify the root cause before proposing fixes.

Core Features & Use Cases

Phase-driven investigation: Four mandatory phases (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation) to systematically uncover root causes.
Defense-in-depth: Encourages multiple validation layers and explicit anti-patterns to resist shortcuts.
Guided usage with examples: Includes practical workflows, checklists, and scenarios to practice systematic debugging.

Quick Start

Use this skill to guide a debugging session when you encounter a bug, test failure, or unexpected behavior, and ensure you follow the four-phase process before proposing fixes.

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 how does it stop symptom fixes?▼

Systematic debugging is a structured approach that enforces phase-driven investigation to identify the root cause before proposing fixes. It stops symptom fixes by requiring evidence-based pattern analysis and hypothesis testing to address the original trigger.

How do I find the root cause of a test failure or production fault?▼

To find the root cause, follow a four-phase investigation process: root cause investigation, pattern analysis, hypothesis testing, and implementation. This ensures you systematically uncover the root cause through evidence rather than applying immediate patches.

What is the best way to investigate unexpected behavior before proposing fixes?▼

The best way to investigate unexpected behavior is using a defense-in-depth approach with multiple validation layers and explicit anti-patterns. This method resists shortcuts and ensures you validate the root cause through structured hypothesis testing.

Can I apply systematic debugging to build failures and performance problems?▼

Yes, systematic debugging applies to any technical issue, including build failures, performance problems, test failures, and production faults. It adapts to any scenario where evidence-based root-cause analysis is needed.

How do I structure a debugging session to ensure I don't take shortcuts?▼

Structure your debugging session using four mandatory phases: root cause investigation, pattern analysis, hypothesis testing, and implementation. This framework enforces systematic investigation and includes explicit anti-patterns to resist premature fixes.

When should I not use a root-cause tracing approach for debugging?▼

Root-cause tracing should not be used when you need an immediate, temporary patch to restore service and lack the time for evidence-based pattern analysis. It is designed for systematic investigation, not quick symptom suppression.