What problem does it solve? Developers often apply quick patches based on pattern-matching instead of finding the actual root cause, which leads to regressions and recurring bugs. This Skill enforces a disciplined investigation process that halts feature work, preserves evidence, and requires root cause confirmation before any fix is written. ## Core Features & Use Cases - Four-Phase Debugging Workflow: Root Cause Tracing, Pattern Analysis, Hypothesis Testing, and test-first Implementation with regression verification. - Fresh Eyes Escape Hatch: After two disproven hypotheses, dispatch a fresh subagent with only the symptom and entry point to break out of anchoring bias. - Defense-in-Depth Guidance: Reference material on adding validation at multiple layers and replacing flaky timeouts with condition-based polling. - Use Case: A test suite fails intermittently in CI. Instead of retrying or patching the assertion, follow the phases to reproduce the failure, trace the call stack back to a race condition, write a failing test that proves the root cause, then apply a minimal fix. ## Quick Start Ask the agent to debug a failing test or error using the systematic debugging process, starting with root cause investigation before any fix.
