reversa-migrate

Orchestrates a six-agent pipeline that converts legacy system specs into migration-ready specifications.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-migrate-ruggery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-migrate
Source: https://github.com/Ruggery/OCR_Cartorio/tree/main/.agents/skills/reversa-migrate
Command: npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-migrate-ruggery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating a legacy system to a modern stack requires coordinated decisions about paradigm, architecture, screens, and parity testing. This Skill orchestrates that entire migration planning pipeline, turning the specs produced by the Reversa discovery flow into a complete, human-approved handoff package for a coding agent. ## Core Features & Use Cases - Six-agent migration pipeline: Sequentially invokes Paradigm Advisor, Curator, Strategist, Designer, Screen Translator, and Inspector, each producing versioned artifacts under _reversa_sdd/migration/. - Human decision gates with resumable state: Pauses after each agent for approval, tracks progress in .state.json, and supports --resume, --regenerate, and --auto modes with documented defaults. - Structured handoff generation: Consolidates ambiguity logs, parity specs, and decision documents into a handoff.md that a coding agent can consume directly. - Use Case: After running /reversa on a legacy COBOL or monolith system, invoke /reversa-migrate to interview stakeholders, decide the target paradigm and topology, plan data migration and cutover, and deliver parity test specs to the team rebuilding the system. ## Quick Start Run /reversa-migrate after /reversa has populated the _reversa_sdd/ directory to start the guided migration pipeline.

Frequently Asked Questions about reversa-migrate

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

FAQPage Schema
How do I plan a legacy system migration with AI agents?▼

Run the Reversa discovery flow first to generate specs in _reversa_sdd/, then invoke /reversa-migrate. It interviews you for a migration brief, runs six specialized agents in sequence, and produces architecture, data migration, cutover, and parity test artifacts.

What artifacts does the Reversa migration pipeline produce?▼

It produces a migration brief, paradigm and topology decisions, target architecture and data models, a data migration plan, screen translation specs, parity test features, an ambiguity log, and a final handoff.md for the coding agent.

Can I resume an interrupted migration pipeline?▼

Yes. The orchestrator persists progress in _reversa_sdd/migration/.state.json. Use --resume to continue from the last checkpoint, or --regenerate=<agent> to redo a specific agent and all downstream artifacts with automatic backup.

Does reversa-migrate work without human interaction?▼

Yes, via the --auto flag, which applies documented defaults for every decision gate and logs each auto-decision in ambiguity_log.md for later review. It always displays the full list of defaults and asks for confirmation before starting.

What happens if the legacy system has no user interface?▼

The Screen Translator agent detects the absence of UI and completes with status skipped, recording the justification in ambiguity_log.md. The pipeline continues to the Inspector and the handoff notes that no screens exist.