What problem does it solve? Reverse-engineering a legacy codebase module by module is slow and error-prone: undocumented business rules, hidden data structures, and complex control flows get lost. This Skill performs deep, structured excavation of each module and produces consistent technical documentation artifacts. ## Core Features & Use Cases - Module-by-module deep analysis: Extracts functions, conditionals, loops, error handling, algorithms, data transformations, and validation logic from each module listed in the reverse-engineering plan. - Structured data dictionary and flowcharts: Generates code-analysis.md, data-dictionary.md, Mermaid flowcharts per module (and per function at the detailed level), plus a machine-readable modules.json following a defined schema. - Confidence labeling and checkpoints: Tags every finding as confirmed, inferred, or gap, and saves per-module checkpoints in .reversa/state.json so long sessions can pause and resume safely. - Use Case: During the excavation phase of a legacy system reverse-engineering project, run this after the scout phase to turn each module's source code into documented algorithms, entities, and business rules for the architect and writer phases. ## Quick Start Analyze the modules listed in .reversa/plan.md and generate the code analysis, data dictionary, and flowcharts into the output folder defined in .reversa/state.json.
