systematic-debugging

Enforce a four-phase debugging workflow to resolve root causes.

Updated Feb 25, 2026

Search Tags:#testing #debugging #framework #phases #hypothesis #root-cause

Ready to run

npx skills add https://github.com/Adrian-opo/multitool-app --skill systematic-debugging-adrian-opo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Adrian-opo/multitool-app/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/Adrian-opo/multitool-app --skill systematic-debugging-adrian-opo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the problem of wasting time on symptom fixes by enforcing a four-phase systematic debugging workflow.

Core Features & Use Cases

Enforces a four-phase process (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation)
Provides explicit rules, anti-patterns, and guardrails to resist shortcuts
Use cases include debugging bugs, test failures, production issues, and integration problems, especially under time pressure

Quick Start

Load the skill and follow Phase 1 through Phase 4 to identify and resolve the root cause before implementing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of a bug instead of just fixing the symptom?▼

Systematic debugging prevents symptom fixes by enforcing a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation, ensuring you identify the underlying issue before applying any fixes.

What is the best way to debug production anomalies under time pressure?▼

The best way to debug production anomalies under time pressure is to use a structured debugging framework with explicit rules and anti-patterns that resist shortcuts, forcing you to validate hypotheses and analyze patterns before proposing a fix.

How do I systematically debug recurring test failures and integration problems?▼

You can systematically debug test failures and integration problems by completing a four-phase process that includes investigating root causes, analyzing failure patterns, forming and testing hypotheses, and finally implementing the verified fix.

Does this systematic debugging approach work for all types of technical issues?▼

Yes, this systematic debugging approach works for any technical issue, including bugs, test failures, production anomalies, and integration problems, by enforcing a root-cause investigation workflow regardless of the specific error type.

When should I avoid quick fixes and use a hypothesis-driven debugging framework?▼

You should avoid quick fixes and use a hypothesis-driven debugging framework whenever you face complex bugs or production anomalies, especially under time pressure where shortcuts are tempting and risk recurring symptom failures.

What are the anti-patterns to watch out for during root cause investigation?▼

Common anti-patterns during root cause investigation include skipping the pattern analysis phase and jumping straight to implementation, which this debugging framework counters with explicit guardrails and escalation paths to ensure thorough resolution.