systematic-debugging

Enforce a four-phase root-cause-first debugging workflow for software issues.

19|2|Updated Mar 21, 2026

Search Tags:#debugging #troubleshooting #defense-in-depth #root-cause-analysis #systematic-debugging #phase-driven

Ready to run

npx skills add https://github.com/bonnguyenitc/antigravity-superpowers --skill systematic-debugging-bonnguyenitc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic-debugging helps engineers diagnose and fix bugs by enforcing a structured, four-phase workflow that targets root causes rather than symptoms.

Core Features & Use Cases

Phase-guided debugging (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to reduce reruns and wasted effort.
Defense-in-depth integration with multiple validation layers and early instrumentation to capture essential context.
Works across code faults, flaky tests, and production incidents, helping teams stabilize systems faster.

Quick Start

Run the four-phase systematic-debugging workflow on the issue to start root-cause analysis before proposing 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 structured, four-phase workflow that targets root causes rather than symptoms. It enforces evidence gathering and root-cause verification before fixes, reducing wasted effort and bug reruns.

How do I debug flaky tests using a phase-driven workflow?▼

Debug flaky tests by applying the phase-driven workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. It mandates evidence gathering and hard-gate confirmation before applying the final fix.

Can I use this root-cause analysis workflow for production incidents?▼

Yes, this root-cause analysis workflow works across code faults, flaky tests, and production incidents. It helps teams stabilize systems faster by integrating defense-in-depth validation and early instrumentation.

What's the best way to stop fixing symptoms instead of root causes?▼

The best way to stop fixing symptoms is enforcing a root-cause-first debugging workflow. It mandates root-cause verification before fixes and a hard-gate confirmation before the Implementation phase to prevent superficial patches.

Does this debugging method require defense-in-depth validation?▼

Yes, this debugging method integrates defense-in-depth with multiple validation layers. It uses early instrumentation to capture essential context and enforces evidence gathering throughout the hypothesis testing phases.

Why does my debugging workflow lack a hard-gate confirmation before fixes?▼

Your debugging workflow lacks a hard-gate confirmation because it does not enforce root-cause verification. The systematic-debugging workflow implements a hard gate before Phase 4 to ensure fixes address verified root causes.