reversa-migrate

Orchestrate a six-agent legacy migration workflow and generate handoff.md artifacts.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-migrate-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-migrate
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-migrate
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-migrate-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the challenge of converting legacy system understanding into operational, traceable migration specifications by coordinating a multi-agent workflow after discovery has already produced the required spec inputs.

Core Features & Use Cases

  • Migration pipeline orchestration: Runs the 6 migration agents in a strict sequence to transform legacy specs into migration-ready targets for coding agents.
  • Human-in-the-loop checkpoints: Enforces approvals at key decision phases (e.g., topology and screen modernization) and supports resuming interrupted migrations safely.
  • Artifact and state management: Validates expected artifacts in _reversa_sdd/, tracks progress in _reversa_sdd/migration/.state.json, consolidates ambiguity items, and generates the final handoff.md.
  • Use case: After running /reversa on a legacy project and generating _reversa_sdd/, use this skill to produce a complete set of migration targets (architecture, domain/data model, screen contracts, parity plan) plus a structured handoff for the coding agent.

Quick Start

Run "/reversa-migrate" after you have executed "/reversa" and generated the _reversa_sdd/ specs.

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 legacy migration workflow after reverse engineering specifications?

You orchestrate a legacy migration workflow by running a multi-agent pipeline that transforms reverse-engineered specifications into coding-ready artifacts. The pipeline runs six migration agents in strict sequence to generate architecture, domain models, and screen contracts.

What is the best way to manage migration state and traceable artifacts across multiple coding agents?

Manage migration state by validating expected artifacts and tracking progress in a centralized state file. This approach tracks pipeline progress, consolidates ambiguity items, and maintains traceability for the final coding handoff.

Do I need human approval gates during legacy system migration?

Human approval gates are required at key decision phases like topology and screen modernization. This human-in-the-loop checkpoint mechanism ensures critical migration decisions are validated before proceeding to final coding handoff generation.

How do I resume an interrupted legacy migration pipeline safely?

You resume an interrupted legacy migration pipeline by leveraging stateful workflow management that tracks progress in a dedicated state file. This allows the multi-agent orchestration to safely restart from the last completed checkpoint.

Can I generate a coding handoff document directly from reverse-engineered legacy specs?

You can generate a coding handoff document by running migration agents that process your reverse-engineered legacy specs. The workflow renders a final handoff file from templates, providing structured targets for the coding agent.

What are the limitations of running migration agents without validating expected legacy discovery artifacts?

Running migration agents without validating expected legacy discovery artifacts risks pipeline failure because the workflow requires populated specification inputs. The orchestration depends on existing reverse-engineered specs to transform them into operational migration targets.