reversa-reconstructor

To generate a bottom-up reconstruction plan, the tool converts specifications stored in `_reversa_sdd/` into an executable `_reversa_sdd/reconstruction-plan.md` file. It requires strict preflight checks for required folders and files before creating the plan from the appropriate template.

Token-preserving execution works by reading only the files explicitly listed in each task's `Lê:` field during implementation. This minimizes context reads to preserve tokens, stopping to confirm whenever a 🔴 gap is found in the specifications.

Yes, you can use migration specifications for project rebuilding. The tool detects if `_reversa_sdd/migration/handoff.md` exists and interactively asks you to choose between original specs, migration specs, or a free-form alternative source before generating the reconstruction plan.

Before starting a specification-driven reconstruction, you need valid Reversa-generated specifications located in `_reversa_sdd/` or `_reversa_sdd/migration/`. The tool enforces strict preflight checks for these required folders and files before allowing any planning or execution to proceed.

You implement tasks one at a time by invoking the skill and replying with INICIAR to create or continue the reconstruction plan. The execution mode then processes tasks sequentially on demand, reading only per-task `Lê:` files to maintain token efficiency.