systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: timequity

Enforce a four-phase root-cause investigation workflow before applying fixes to bugs and test failures.

6|Updated Dec 7, 2025

Search Tags:#debugging #quality-assurance #root-cause #four-phase #root-cause-investigation

Ready to run

npx skills add https://github.com/timequity/plugins --skill systematic-debugging-timequity

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and patch symptoms. This Skill enforces a four-phase framework to identify root causes before implementing fixes, reducing rework and increasing reliability.

Core Features & Use Cases

Four phases: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation
Iron Law: No fixes without complete root-cause investigation
Clear gates to pause and reassess before moving forward
For multi-component systems: trace data flow and verify environment/config propagation

Quick Start

Run the four-phase process on a reported issue, starting with Phase 1 (Root Cause Investigation) before proposing any patch.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I fix bugs without wasting time on random patches?▼

Root-cause debugging enforces a four-phase investigation framework—evidence collection, reproducible steps, pattern analysis, and hypothesis testing—before implementing any fix. This systematic approach eliminates rework by identifying the actual source of the problem, not just symptoms.

What's the best way to investigate test failures and unexpected software behavior?▼

Apply the four-phase root-cause investigation process: collect evidence from logs and environment state, reproduce the issue consistently, analyze patterns across components, and test your hypothesis before deploying. This gates fixes at each phase to catch incomplete diagnoses early.

How do I troubleshoot performance problems and runtime anomalies in production?▼

Root-cause debugging traces data flow across multi-component systems, verifies environment and config propagation, and validates reproducible steps before patching. The framework prevents misattribution of symptoms to wrong components and reduces mean time to resolution.

When should I use root-cause investigation instead of quick fixes?▼

Root-cause investigation applies to all bugs, build failures, integration failures, and performance issues across development, testing, and production. Quick fixes create technical debt and recurring failures; systematic investigation prevents the same bug from resurging.

What's the difference between patching symptoms and fixing root causes?▼

Symptom patches hide the underlying problem and waste time on rework when the issue resurfaces. Root-cause debugging identifies the actual source through evidence-driven investigation, ensuring fixes are durable and reducing total debugging cycles.

Can I use root-cause debugging across different tech stacks and platforms?▼

Yes. The four-phase framework applies to bugs, test failures, and runtime anomalies in any technology stack—web services, distributed systems, embedded software, and more. The process is independent of language, framework, or infrastructure.