systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: phife726

Enforce a four-phase root-cause workflow to debug production outages and flaky tests.

Updated Mar 8, 2026

Search Tags:#debugging #defense-in-depth #systematic #traceability #phases #root-cause #multi-component

Ready to run

npx skills add https://github.com/Phife726/ds_agent --skill systematic-debugging-phife726

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When debugging complex bugs, you need a repeatable process that prioritizes root cause over quick fixes and reduces wasted time.

Core Features & Use Cases

Phase-based approach: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis & Testing, Phase 4 Implementation.
Anti-patterns and defenses to resist hurried fixes, with explicit stop-and-reanalyze guidance.
Real-world use cases: debugging production outages, flaky tests, and multi-component systems.

Quick Start

Run the four-phase framework on the current issue, starting with root-cause investigation before proposing any fix, and consult the defense-in-depth guidelines when data flows across components.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a systematic approach to root-cause debugging for production outages?▼

Systematic debugging enforces a four-phase root-cause workflow—investigation, pattern analysis, hypothesis testing, and implementation—before proposing any fix. It applies defense-in-depth validation to prevent hurried patches and resolves complex multi-component outages.

How do I debug flaky tests across multi-component systems?▼

Debug flaky tests by applying a phased root-cause workflow that reproduces the behavior issue, analyzes patterns across components, and tests hypotheses. Defense-in-depth guidelines validate data flow to ensure the fix targets the actual root cause.

How to stop fixing symptoms and find the root cause of behavior issues?▼

Stop fixing symptoms by enforcing strict anti-pattern checks that halt the process for reanalysis. The framework requires completing Phase 1 root-cause investigation and Phase 2 pattern analysis before allowing any hypothesis or implementation.

Can I use this systematic debugging method for multi-component data flow issues?▼

Yes, this method explicitly supports multi-component systems. It provides defense-in-depth guidelines specifically designed to validate and trace data as it flows across components during the root-cause investigation and hypothesis testing phases.

What's the best way to structure a debugging workflow for complex software bugs?▼

The best way to structure debugging is using a four-phase workflow: reproduce and investigate the root cause, analyze patterns, test hypotheses, and implement the fix. This traceable process reduces wasted time and resists hurried solution proposals.

When should I reanalyze during the root-cause debugging process?▼

You should reanalyze when encountering identified anti-patterns that trigger explicit stop-and-reanalyze guidance. This defense mechanism prevents jumping to premature solutions and ensures you complete the investigation and pattern analysis phases before proceeding.