What problem does it solve?
This Skill provides a rigorous, four-phase framework for debugging, preventing wasted time on symptom fixes and ensuring that only root causes are addressed. It combats the urge to guess or rush, even under pressure, leading to more effective and lasting solutions.
Core Features & Use Cases
- Four-Phase Framework: Guides through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, ensuring a thorough approach.
- Pressure-Resistant Mandates: Includes "Iron Laws" and explicit "STOP" directives to prevent shortcuts and rationalizations, even in emergencies.
- Evidence-Based Debugging: Emphasizes gathering diagnostic instrumentation and tracing data flow in multi-component systems before proposing any fixes.
- Architectural Review Trigger: If multiple fixes fail, the skill prompts a critical review of the underlying architecture, preventing endless symptom patching.
- Use Case: When a critical production bug arises, or a complex test fails unexpectedly, use this skill to methodically diagnose the problem, identify the true root cause, and implement a robust solution, avoiding costly rework and ensuring stability.
Quick Start
You: I've encountered a bug in the payment service. Let's use the systematic-debugging skill to find the root cause.
