What problem does it solve? Before fixing a bug or designing a feature, engineers need facts about what the existing code actually does, what it shares, and who depends on it. This Skill performs a task-scoped recon of a codebase and writes an evidence-cited analysis document, replacing guesswork with verified findings. ## Core Features & Use Cases - Task-Scoped Tracing: Follows the call path from the entry point to the behavior in question, citing every hop as path:line, without auditing unrelated code. - Root-Cause Chain for Bugs: Walks Expected Flow, Actual Flow, Failure Point, Root Cause, and Corrected Flow in order, labeling unproven causes as hypotheses with confirming evidence. - Shared-Code and Contract Mapping: Builds a mandatory table of shared symbols with their consumers, marked Structural or Behavioral, and lists external contracts flagged UNVERIFIED when not confirmed. - Use Case: Before modifying a checkout validation function, run this Skill to produce void/<task-slug>/analysis.md showing the flow, every consumer of the shared validation logic, and the API contracts it relies on. ## Quick Start Ask the assistant to analyze the code path behind a specific bug or planned change and write the findings to void/<task-slug>/analysis.md.
