reversa-archaeologist

To generate operational specifications from legacy code, this Skill reverse-engineers modules to extract control flow, algorithms, and data structures, producing traceable artifacts and a structured modules.json for downstream AI agents.

Yes, you can build a data dictionary from undocumented source modules. It analyzes legacy code to produce a structured data model containing fields, types, requirements, and defaults when the selected documentation level supports it.

The best way to extract control flow and algorithms from legacy projects is through deep code excavation, which analyzes each module individually to capture validation logic and operational truths for deterministic specification generation.

During reverse engineering, module analysis handles checkpoints by reading Reversa state and plan files, then updating checkpoints after each module is processed to ensure traceable and resolvable spec generation.

Yes, you need Reversa state and plan files before starting module analysis. The Skill targets legacy projects during the excavation phase by reading these files to identify which modules require analysis and documentation generation.

When generating specifications for large legacy codebases, processing operates module-by-module and saves checkpoints after each one, so limitations depend on configuring the appropriate documentation level and managing the output folder structure.