systematic-debugging

Debug software issues through a four-phase root-cause investigation process.

160|16|Updated Dec 4, 2024

Search Tags:#debugging #quality-assurance #root-cause #systematic-debugging #software-testing #phase-checklist

Ready to run

npx skills add https://github.com/MaggieAppleton/maggieappleton.com-V3 --skill systematic-debugging-maggieappleton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/MaggieAppleton/maggieappleton.com-V3/tree/main/.claude/skills/planning-and-product/systematic-debugging
Command: npx skills add https://github.com/MaggieAppleton/maggieappleton.com-V3 --skill systematic-debugging-maggieappleton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps teams avoid chasing symptoms by enforcing a root-cause-first workflow and documenting explicit phases and guardrails.

Core Features & Use Cases

Four-phase framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) that must be completed before fixes
Anti-patterns and defensive practices to resist shortcutting under pressure
Supporting techniques and references to deepen debugging fidelity across projects
Real-world impact: faster issue resolution with higher first-time fix rate

Quick Start

Read the overview, then follow the four phases in order (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation) before proposing any 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 find root causes?▼

Systematic debugging is a root-cause-first workflow that enforces a four-phase process—Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation—to identify root causes before proposing fixes and reduce symptom-only patches.

How do I debug software bugs systematically without chasing symptoms?▼

To debug software bugs systematically, follow the four phases in order: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. You must complete all phases before proposing any fixes to avoid chasing symptoms and causing rework.

What's the best way to stop developers from shortcutting the debugging process under pressure?▼

The best way to stop shortcutting under pressure is to apply explicit anti-patterns and defensive practices that enforce a root-cause-first workflow, ensuring the four-phase debugging process is completed before any fixes are implemented.

Can I use a systematic debugging approach for any type of test failure or unexpected behavior?▼

Yes, you can apply systematic debugging to any bug, test failure, or unexpected behavior across software projects and teams. The four-phase framework is designed to generalize across different software contexts.

Why do my software patches fail to fix the original issue and require rework?▼

Software patches fail and require rework when they address symptoms instead of root causes. Applying a systematic debugging framework enforces root cause identification before implementation, increasing the first-time fix rate.

What are the limitations of a systematic debugging approach for software testing?▼

The main limitation of systematic debugging is the time required to complete the four phases—Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation—before proposing fixes, which may feel slow under high-pressure situations.