What problem does it solve? Debugging and incident analysis often rely on guesswork, lost context, and unverified assumptions. This Skill enforces a disciplined forensic workflow that reconstructs what happened from available evidence, grades every finding as Confirmed, Deduced, or Hypothesized, and produces a persistent case file another engineer can pick up cold. ## Core Features & Use Cases - Evidence-graded investigation: Anchors analysis in a Confirmed stronghold, traces causality backward from symptoms, and runs refutation passes before confirming hypotheses. - Persistent case file: Initializes a structured Markdown case file (evidence inventory, timeline, hypotheses, backlog, conclusion with confidence level) that survives interruptions and supports follow-up sessions. - Dual-mode operation: Handles both symptom-driven defect chasing (tickets, logs, stack traces) and symptom-free code area exploration to build a mental model before making changes. - Use Case: A user reports a failing escrow release on a Stellar-based trade platform. Activate the skill with the error message; it anchors on the confirmed error, maps the evidence perimeter across logs and version control, traces the root cause through the Soroban contract call chain, and delivers a case file with a High-confidence conclusion and fix direction. ## Quick Start Ask the agent to investigate a bug by providing a ticket ID, error message, log file path, or code area name, for example: investigate why the escrow release transaction fails after delivery confirmation.
