Verified:GitHub

reversa-reconstructor

Generates executable bottom-up reconstruction plans from Reversa specifications and tracks tasks permissively with strict file reading.

Updated May 5, 2026

Search Tags:#migration #token efficiency #task planning #agent skill #reconstruction #spec-to-code

Ready to run

npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-reconstructor-alexandrepontesjr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-reconstructor
Source: https://github.com/AlexandrePontesjr/calculadora-Juridica/tree/main/.agents/skills/reversa-reconstructor
Command: npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-reconstructor-alexandrepontesjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns Reversa-generated specifications into an executable, step-by-step reconstruction plan, so you can reimplement the system from the ground up with minimal token usage and controlled execution.

Core Features & Use Cases

Bottom-up reconstruction planning: Converts Reversa specs into a task sequence executed one task at a time.
Migration-aware workflow: Detects whether to reconstruct from original specs or migration specs, including handling migration-in-progress situations.
Token-preserving execution discipline: Reads only the files required by each task’s Lê: list, pauses for gaps, and updates the plan incrementally.

Quick Start

Activate it with /reversa-reconstructor and follow the prompts to choose the reconstruction source (original, migration, or other) when applicable.

Frequently Asked Questions about reversa-reconstructor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an executable reconstruction plan from software specifications?▼

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.

How do I handle migration-based reconstruction when porting a legacy system?▼

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.

Do I need a specific directory structure to start spec-to-code reconstruction?▼

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.

What is the best way to control token usage during agent-driven code reconstruction?▼

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.

Why does the reconstruction process pause before completing all planned tasks?▼

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.

Can I resume a reconstruction plan after pausing for missing specifications?▼

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.