dead-reckoning

What problem does it solve?

Structured analysis partner for complex legacy codebases. Use when the user wants to understand existing behavior, trace a call tree, investigate a bug, or answer a specific architectural question in a system that is hard to read (Clojure, verbose Java, Kotlin monorepos, or any poorly structured codebase). This skill drives the traversal session — enforcing a central question, managing a living knowledge base of facts and spikes, producing explicit coverage evidence, and finalizing a spike document at the end. The human validates; the agent traverses and translates. Activate on phrases like "analisa esse código", "quero entender como funciona", "como isso está implementado", "me ajuda a traçar", "trace this call", "how is this built", "what does X do in production", or any request to investigate existing code before making a decision or raising a PR. Do not use for greenfield design or planning without a codebase — use thinking-partner for that.

Core Features & Use Cases

• Centralizes a focused central question to drive a structured traversal of a codebase.
• Manages a living knowledge base of facts and spikes, with explicit evidence and traceability.
• Produces a final spike document that captures findings, decisions, and actionable next steps.
• Supports human validation and collaborative interpretation to translate traversal results into engineering decisions.

Quick Start

State a central question about the codebase and initiate the traversal session.