reversa-reconstructor

Name: reversa-reconstructor
Availability: InStock
Author: Ricardo

Generate executable bottom-up reconstruction plans from Reversa specifications.

Updated May 16, 2026

Search Tags:#planning #spec-driven #code generation #migration #dependency graph #legacy modernization #reconstruction

Ready to run

npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-reconstructor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-reconstructor
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-reconstructor
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-reconstructor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns reverse-engineered specifications into an executable, bottom-up reconstruction plan and implementation workflow.

Core Features & Use Cases

Bottom-up reconstruction planning: Creates a task-by-task plan derived from the Reversa SDD, respecting dependencies and ensuring infrastructure comes first.
Migration-aware planning: Supports planning from either original specs or migration specs when _reversa_sdd/migration/handoff.md is present, and enforces user choice.
Token-preserving, incremental execution: Reads only the files declared in each task’s "Lê" list, updates the plan as tasks complete, and pauses on gaps.

Quick Start

Run the reversa-reconstructor skill by asking to initiate a full reconstruction from the specs available in _reversa_sdd/.

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 reverse-engineered software specifications?▼

Generate an executable bottom-up reconstruction plan by deriving task sequences from Reversa SDD files, ensuring infrastructure is built first and dependency-driven unit sequencing is respected throughout the legacy modernization process.

How does spec-driven reconstruction handle migration when original specs are unavailable?▼

Spec-driven reconstruction supports migration by reading handoff artifacts from the migration directory, enforcing user-confirmed source selection to apply migration specs instead of original specs for rebuilding legacy software.

What is the best way to control token usage during incremental legacy code generation?▼

Control token usage during legacy code generation by enforcing strict minimal-file reading, where only the files declared in each task's reading list are accessed, updating the reconstruction plan as tasks complete incrementally.

When should I pause a bottom-up reconstruction workflow to avoid inventing undocumented behavior?▼

Pause a bottom-up reconstruction workflow when gaps in the Reversa specifications are detected, utilizing gap-driven pausing to prevent inventing undocumented behavior during legacy modernization and cutover planning.

Do I need dependency graph analysis to sequence tasks in a bottom-up software reconstruction?▼

Yes, dependency graph analysis is required to sequence tasks in bottom-up software reconstruction, ensuring dependency-driven unit sequencing places foundational infrastructure before higher-level components in the executable plan.

Can I use reversa-reconstructor for cutover and parity planning during legacy modernization?▼

Yes, reversa-reconstructor handles cutover and parity planning during legacy modernization by generating executable reconstruction plans that include cutover milestones and parity checks derived from the Reversa specifications.