reversa-migrate

Orchestrate legacy-to-modern migration pipelines from _reversa_sdd/ specifications with checkpoint approvals.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-migrate
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-migrate
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns already-discovered legacy specifications into an actionable, human-gated migration plan in a modern stack, reducing guesswork and rework during reconstruction.

Core Features & Use Cases

  • Pipeline orchestration: Coordinates the full migration team (Paradigm Advisor → Curator → Strategist → Designer → Screen Translator → Inspector) to produce migration-ready specs.
  • Human approval checkpoints: Manages approvals for topology and UI translation decisions, pausing when decisions are required.
  • Migration handoff package: Consolidates outputs into a final handoff.md that guides the coding agent on what to implement next.
  • Safety guardrails: Enforces required legacy artifacts in _reversa_sdd/ and blocks execution when discovery is incomplete.

Quick Start

Run reversa-migrate after you have executed /reversa so _reversa_sdd/ is populated with the legacy specs, then follow the human approval prompts until handoff.md is generated.

Frequently Asked Questions about reversa-migrate

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

FAQPage Schema
How do I orchestrate a full legacy to modern stack migration?

Legacy migration orchestration coordinates a deterministic agent sequence across paradigm, strategy, architecture, and screen translation stages to produce migration-ready specs for a modern stack.

What is the best way to plan a legacy reconstruction using discovered specifications?

Legacy reconstruction from specs applies already-produced discovery artifacts to generate an actionable, human-gated migration plan, reducing guesswork and rework during the modern reconstruction process.

Do I need to run discovery before starting a spec transformation migration?

Yes, spec transformation requires strict precondition checks and will block execution if the required legacy artifacts in the discovery directory are incomplete or missing.

How does human approval work during UI screen translation and architecture planning?

Human approval checkpoints pause the pipeline during architecture topology and UI screen translation decisions, requiring manual approval before the next agent in the sequence can execute.

What outputs do I get after running a migration orchestration pipeline?

Migration orchestration generates migration outputs in a designated directory and consolidates them into a final handoff package that guides the downstream coding agent on what to implement.

Can I resume an interrupted migration pipeline without losing progress?

Yes, the migration pipeline persists its execution state in a state file, allowing the ordered agent sequence to resume securely after human approval checkpoints or interruptions.