reversa-reconstructor

Bottom-up legacy system reconstruction from specifications converts Reversa-generated specs into an executable, incremental plan that preserves traceability by executing tasks one step at a time and pausing when gaps appear so you maintain control over the reimplementation workflow.

The best way to plan a legacy migration using target-stack specifications is to leverage migration handoff artifacts. The reconstruction process detects these artifacts, interactively prompts you to select the specs source, and follows the defined migration strategy and topology decisions to generate the plan.

To execute a software reconstruction plan while preserving token usage, the process applies strict file-scoped reading per task and pauses when gaps appear. This task-by-task execution model reads only the required files for each step to minimize context overhead.

Yes, legacy modernization reconstruction requires a _reversa_sdd/ directory. The process performs prerequisite checks for this folder and persists the executable reconstruction plan and status updates directly in _reversa_sdd/reconstruction-plan.md.

Yes, you can reimplement a legacy system faithfully using original operational specs. The reconstruction workflow supports faithful reconstruction directly from original specs when migration handoff artifacts are absent, ensuring an accurate bottom-up reimplementation.