systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: ironbob

Provides a four-phase root-cause debugging framework for technical issues.

Updated Mar 21, 2026

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

Ready to run

npx skills add https://github.com/ironbob/SuperPower_light --skill systematic-debugging-ironbob

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers identify root causes before applying fixes, reducing waste and rework.

Core Features & Use Cases

Four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation.
Anti-patterns and defense-in-depth guidelines to prevent symptom-focused fixes.
Works across bugs, test failures, production issues, and integration problems.

Quick Start

Load the skill and follow Phase 1 checklist to begin root-cause investigation.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is root-cause debugging and how does it stop me from patching symptoms?▼

Root-cause debugging identifies the underlying origin of bugs before applying fixes. It uses a four-phase process—investigation, pattern analysis, hypothesis testing, and implementation—to prevent superficial symptom patching and reduce rework.

How do I debug test failures systematically without guessing the fix?▼

Debug test failures systematically by following a structured four-phase process. Commit to Phase 1 root-cause investigation first, analyze patterns, form hypotheses, and validate data with defense-in-depth patterns to ensure accurate implementation.

What's the best way to troubleshoot production issues to prevent regressions?▼

The best way to troubleshoot production issues is applying a disciplined four-phase methodology. Documenting findings and using defense-in-depth patterns validates data and prevents regressions by ensuring fixes target true root causes.

Can I use this systematic debugging process for integration problems?▼

Yes, this systematic debugging process applies directly to integration problems. It provides a repeatable methodology for disciplined troubleshooting across bugs, test failures, production issues, and integration issues.

Why should I complete Phase 1 before fixing a bug?▼

Completing Phase 1 root-cause investigation before fixing a bug ensures you understand the actual origin. This commitment stops symptom-focused fixes, reducing waste and rework by validating hypotheses through pattern analysis first.

When should I avoid symptom-focused fixes during debugging?▼

Avoid symptom-focused fixes whenever debugging complex bugs or production issues. Instead, identify root causes first using a four-phase process and defense-in-depth guidelines to validate data, which prevents recurring regressions.