systematic-debugging

Guide four-phase root-cause investigation before implementing fixes.

Updated Dec 4, 2025

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

Ready to run

npx skills add https://github.com/jr2804/prompts --skill systematic-debugging-jr2804

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and fix the root cause of failures instead of patching symptoms, reducing time wasted on guesswork.

Core Features & Use Cases

Four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, with explicit stopping rules.
Defense-in-depth: Encourages validation at multiple layers to prevent regression and hidden failures.
Templates & references: Includes checklists and references for tracing data flow and root causes.

Quick Start

Load the skill, read the overview, complete Phase 1 before proposing any fixes, then proceed through Phase 2–4 to resolve the issue.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic root cause debugging and how does it work?▼

Systematic root cause debugging identifies and fixes the actual source of failures rather than patching symptoms. It works by enforcing a four-phase investigation—Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation—before any fixes are proposed.

How do I stop guessing and systematically find the root cause of a bug?▼

To find the root cause of a bug, you must complete a thorough investigation phase before proposing any fixes. This systematic debugging approach uses explicit stopping rules, phase-by-phase checklists, and data flow tracing to eliminate guesswork and ensure the source is identified.

What is the best way to prevent regressions when fixing unexpected software behavior?▼

The best way to prevent regressions is applying defense-in-depth validations during bug resolution. This systematic debugging method enforces multi-layer validation checks across the implementation phase to catch hidden failures and stop regressions before they occur.

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

Yes, this systematic debugging method applies across any bug, test failure, or unexpected behavior. It provides a universal four-phase process with explicit rules and checklists that guide you through investigating and resolving diverse software failures.

Do I need any specific frameworks or tracing tools to start root cause investigation?▼

No specific frameworks or external tracing tools are required to start root cause investigation. This debugging skill provides built-in templates and references for tracing data flow, requiring only a willingness to complete the root-cause phase before proposing fixes.