reversa-reconstructor

To generate an executable reconstruction plan from software specifications, you can use a spec-to-code workflow that converts Reversa specifications into a bottom-up task sequence, executing each step individually with strict file reading limits.

Migration-based reconstruction detects whether to rebuild from original specs or migration handoff artifacts. The workflow handles migration-in-progress situations by selecting the correct spec source, ensuring continuity when porting legacy systems to new architectures.

Spec-to-code reconstruction requires validating preconditions like the presence of a `_reversa_sdd/` directory before starting. This ensures the necessary specification artifacts are available to generate the executable bottom-up reconstruction plan.

Token-preserving execution discipline reads only the files required by each task's `Lê:` file list, pausing for gaps and updating the plan incrementally. This minimizes token usage while maintaining strict execution control during bottom-up reconstruction.

The reconstruction process pauses on any reconstruction gaps encountered during execution. This strict execution discipline ensures each task's preconditions and file dependencies are fully resolved before proceeding to the next step in the plan.

Plan continuation allows resuming a reconstruction plan after pausing. The workflow supports optional migration-based reconstruction paths, letting you pick up from the last completed task once missing files or gaps are resolved.