harness:systematic-debugging

What problem does it solve?

Prevents wasted effort and recurring regressions by forcing disciplined root-cause investigation before any code or configuration changes.

Core Features & Use Cases

• Root-cause-first debugging: Requires completing a structured investigation before proposing fixes, emphasizing evidence over guesses.
• Phase-based workflow: Guides Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and then Implementation with validation.
• Multi-component evidence gathering: Directs you to instrument boundaries (CI→build→signing, API→service→DB, etc.) to pinpoint which layer breaks.
• ADR and incident documentation guardrails: Enforces incident note conventions and mandates ADR invalidation updates when assumptions are broken.

Quick Start

Use the skill when a test fails or behavior is unexpected, and tell the AI: “Debug this failure using harness:systematic-debugging—start with root-cause investigation, then produce an incident note under docs/incidents with symptom, reproduction, root cause, and fix (or escalation).”