reversa-reconstructor

To generate a reconstruction plan from specifications, you need a tool that converts SDDs into an ordered task list with explicit readiness criteria. This Skill processes Reversa specs in the `_reversa_sdd/` directory to create an audit-defensible, bottom-up reconstruction plan.

Rebuilding a legacy application bottom-up requires executing reconstruction tasks sequentially based on declared file dependencies. This Skill executes tasks one at a time, reading only the files specified in each task's Reads list to preserve token context and maintain auditability.

Yes, migration-aware rebuilding supports both original specs and migration specs. The Skill provides interactive source selection to handle migration state, allowing you to create or continue an existing reconstruction plan from either specification type.

Bottom-up reconstruction planning requires Reversa output copied into the `_reversa_sdd/` directory. You must verify these SDD prerequisites exist before selecting a reconstruction source and generating the `_reversa_sdd/reconstruction-plan.md` file.

Auditability during legacy codebase reconstruction is ensured by executing tasks strictly based on each task's declared Reads list. This token-preserving approach generates a step-by-step, audit-defensible plan that tracks exactly which files are accessed during the rebuild.

Reconstruction task execution requires verifying `_reversa_sdd/` prerequisites and a valid `reconstruction-plan.md`. If the migration state is incomplete or the declared Reads list references missing files, the sequential execution will halt to preserve token context and auditability.