What problem does it solve? Debugging production issues, failing tests, and unclear bugs often devolves into log fishing, untested guesses, and endless reproduction attempts. This Skill enforces a disciplined investigation loop: define the symptom precisely, gather evidence before theorizing, test hypotheses against a ledger, and stop on a confirmed root cause or escalate with a ruled-out list. ## Core Features & Use Cases - Structured Symptom Definition: Captures expected-vs-actual behavior, blast radius, frequency, and done criteria before any investigation begins. - Bounded Hypothesis Loop: Tests candidate root causes against logs, traces, metrics, and code paths, maintaining a confirmed/ruled-out/inconclusive ledger with budget caps to prevent infinite loops. - RCA and Handoff Packaging: Produces a root cause analysis with fix, prevention actions, and escalation paths to councils or human approval gates for high-risk or ambiguous cases. - Use Case: A developer facing a failing integration test in CI runs the workflow in lite mode to define expected-vs-actual behavior, trace the implicated code path, and confirm the root cause with a targeted fix, all within one hypothesis loop. ## Quick Start Investigate this failing test by defining the symptom, gathering evidence from logs and recent changes, and confirming the root cause before proposing a fix.
