reversa-reconstructor

To generate an executable reconstruction plan from software specifications, use a bottom-up planning approach that parses Reversa specs into sequential tasks. The plan executes one task at a time on demand, reading only declared files to preserve tokens and pausing for any missing gaps.

Bottom-up reconstruction is a workflow that rebuilds an existing system from captured software specs by executing granular tasks sequentially. It enforces strict execution fidelity, ensuring the implementation matches exactly what the specifications declare without deviating from the original plan.

Yes, you can reconstruct a repository using migration specifications. The workflow detects whether migration handoff specs exist and prompts you to choose between sourcing the reconstruction from the original software specs or the alternative migration specs.

To start executing a reconstruction plan, run the workflow in your project directory, respond to any source-choice prompts, and type INICIAR to trigger the first task. The system carries out each step sequentially, preserving context between executions.

Yes, the reconstruction workflow pauses if required input files are missing. It enforces strict execution requirements by reading only files declared in each task's designated read field, halting safely whenever it encounters gaps rather than proceeding with incomplete data.

The best way to preserve token usage during automated code generation from specs is to execute a bottom-up plan that restricts file reading to only those explicitly declared in each task. This prevents unnecessary context loading and ensures efficient, controlled repository automation.