What problem does it solve? Debugging and incident analysis often rely on guesswork, scattered notes, and unverified assumptions. This Skill turns bug reports, logs, and unfamiliar code areas into structured, evidence-graded case files that another engineer can pick up cold, with every finding labeled Confirmed, Deduced, or Hypothesized. ## Core Features & Use Cases - Evidence-graded investigation: Every finding is cited with path:line, log timestamps, or commit hashes, and hypotheses are tracked with explicit confirm/refute criteria rather than deleted. - Structured case file lifecycle: Initializes a persistent case file from a template, maps the evidence perimeter, traces causality and timelines, and finalizes with a confidence-rated conclusion and hand-off brief. - Dual-mode operation: Handles both symptom-driven defect chasing (tickets, stack traces, logs) and symptom-free code area exploration to build a mental model before making changes. - Use Case: A user pastes a production stack trace and asks what caused the incident. The Skill opens a case file, anchors on the first Confirmed error, traces the caller chain across the source, and delivers a root-cause conclusion with a reproduction plan. ## Quick Start Investigate why the checkout endpoint returns a 500 error using the attached server log and produce an evidence-graded case file.
