systematic-debugging

Apply a four-phase framework to identify and resolve root causes of technical issues.

Updated Nov 18, 2025

Search Tags:#architecture #debugging #root cause #troubleshooting #systematic #test failure

Ready to run

npx skills add https://github.com/conejoRojo/DeployTime --skill systematic-debugging-conejorojo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/conejoRojo/DeployTime/tree/main/_agent/skills/systematic-debugging
Command: npx skills add https://github.com/conejoRojo/DeployTime --skill systematic-debugging-conejorojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill prevents the common pitfall of applying superficial patches to symptoms, which often leads to wasted time, recurring issues, and the introduction of new bugs.

Core Features & Use Cases

Root Cause Mandate: Enforces a strict four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to ensure the underlying issue is resolved.
Anti-Pattern Detection: Identifies and warns against common debugging shortcuts like "quick fixes" or "shotgun debugging" that feel productive but are ultimately destructive.
Use Case: When a production API fails intermittently, use this skill to trace the data flow across component boundaries, identify the specific failing layer, and implement a permanent fix rather than just adding a retry loop.

Quick Start

Activate the systematic-debugging skill to begin a structured investigation of the current test failure or production bug.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a systematic debugging framework for finding root causes?▼

A systematic debugging framework enforces a strict four-phase process—Investigation, Pattern Analysis, Hypothesis, and Implementation—to identify and resolve the root cause of technical issues rather than applying superficial patches to symptoms.

How do I debug intermittent production API failures across multiple components?▼

To debug intermittent production API failures, trace the data flow across component boundaries to identify the specific failing layer, form an evidence-based hypothesis, and implement a permanent architectural fix rather than relying on quick-fix retry loops.

What's the best way to stop recurring test failures caused by shotgun debugging?▼

The best way to stop recurring test failures is to replace shotgun debugging with anti-pattern detection, enforcing evidence-based hypothesis testing and architectural validation to ensure permanent resolution of the underlying issue.

When do I need a root cause investigation process for unexpected system behavior?▼

You need a root cause investigation process when facing complex system debugging, multi-component integration errors, or scenarios where quick-fix rationalization risks introducing new bugs or wasting time on recurring issues.

How do I validate a debugging hypothesis before implementing a fix?▼

You validate a debugging hypothesis by systematically gathering evidence during the investigation phase, analyzing failure patterns, and testing the hypothesis against architectural constraints before moving to the implementation phase.

Why does adding quick fixes and patches make software bugs harder to resolve?▼

Quick fixes and patches make bugs harder to resolve because they target symptoms instead of root causes, leading to wasted time, recurring issues, and the introduction of new bugs through superficial changes that bypass systematic investigation.