systematic-debugging

Diagnose bugs through a four-phase root-cause investigation process.

7|1|Updated Feb 1, 2026

Search Tags:#debugging #defense-in-depth #systematic #root-cause #engineering-process #bug-triage

Ready to run

npx skills add https://github.com/cloudfieldcz/cf-powers --skill systematic-debugging-cloudfieldcz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, four-phase approach to diagnosing bugs and failures, ensuring root causes are found before fixes.

Core Features & Use Cases

Phase-driven investigation (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) with explicit stop rules to prevent shortcuts
Anti-patterns, defense-in-depth, and stack-trace instrumentation guidelines that improve reliability and reproduce failures
Real-world usage examples and validation tests to train agents on systematic debugging practices

Quick Start

Load the skill and begin with Phase 1 to start 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 systematic debugging and when should I use it for root-cause analysis?▼

Systematic debugging enforces a four-phase process—Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation—with explicit stop rules to prevent shortcut symptom fixes. It applies to development, testing, and production incidents like flaky tests or performance regressions.

How do I debug flaky tests and performance regressions without applying shortcut fixes?▼

Debug flaky tests and performance regressions by following a four-phase process that uncovers root causes before applying fixes. This enforces disciplined data-flow analysis, phase-by-phase validation, and defense-in-depth checks to prevent shortcut symptom patches.

What is the best way to find a bug's root cause instead of just fixing the symptom?▼

The best way to find a bug's root cause is using a phase-driven investigation with explicit stop rules. This approach enforces disciplined data-flow analysis and defense-in-depth checks, ensuring you validate the underlying issue before implementing a fix.

How does defense-in-depth apply to bug triage and systematic root-cause investigation?▼

Defense-in-depth in bug triage improves reliability by adding stack-trace instrumentation guidelines and validation tests. These checks prevent premature symptom fixes by ensuring the root cause is fully reproduced and verified before moving to the implementation phase.

Can I use this systematic debugging process for production incidents as well as local development?▼

Yes, you can use this systematic debugging process for production incidents, local development, and testing. It applies to diagnosing failures like flaky tests and performance regressions by enforcing phase-by-phase validation regardless of the environment.

Why do my bug fixes keep recurring when I patch the symptom instead of the root cause?▼

Bug fixes recur when you patch symptoms instead of the root cause because the underlying fault remains. A four-phase systematic debugging process with explicit stop rules enforces data-flow analysis to uncover and eliminate the true origin.