reversa-migrate

Orchestrate a six-agent migration pipeline to transform discovery specifications into handoff.md files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the fragmentation and loss of context during legacy system migrations by providing a structured, multi-agent pipeline that ensures every aspect of the legacy system is accounted for and translated into modern specifications.

Core Features & Use Cases

  • Multi-Agent Orchestration: Coordinates six specialized agents (Paradigm Advisor, Curator, Strategist, Designer, Screen Translator, Inspector) to handle different facets of the migration.
  • Stateful Pipeline: Maintains a persistent state across sessions, allowing for safe pauses, human-in-the-loop approvals, and incremental progress.
  • Use Case: Use this when you have a legacy system analyzed by the Reversa discovery flow and need to generate a comprehensive handoff document for a development team to rebuild the system in a modern stack.

Quick Start

Initiate the migration pipeline by running the reversa-migrate command in your terminal after the discovery phase is complete.

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 system migration to generate modern architectural requirements?

Legacy system migration is orchestrated by transforming discovery specifications into modern architectural and functional requirements using a structured, six-agent sequence pipeline. It operates on the _reversa_sdd/ directory to ensure complete context translation.

What is the best way to maintain state across sessions during a legacy system modernization?

Legacy system modernization maintains a persistent state across sessions through a stateful pipeline. This allows for safe pauses, incremental progress tracking, and human-in-the-loop approvals at defined validation checkpoints.

Do I need a discovery specification before starting a multi-agent migration pipeline?

A discovery specification is required before starting the migration pipeline. The pipeline specifically transforms legacy system discovery outputs into a comprehensive handoff.md file for development teams.

How does the six-agent sequence work for translating legacy systems into modern functional requirements?

The six-agent sequence works by coordinating specialized agents—Paradigm Advisor, Curator, Strategist, Designer, Screen Translator, and Inspector—to handle distinct migration facets. This structured coordination ensures every legacy aspect is translated into modern specifications.

Can I pause the system modernization pipeline for human-in-the-loop checkpoint validation?

The system modernization pipeline supports pausing for human-in-the-loop checkpoint validation. Its stateful architecture enforces strict adherence to validation points, ensuring safe approvals before progressing to the next agent phase.

What output file does the migration pipeline produce for development teams?

The migration pipeline produces a comprehensive handoff.md file for development teams. This document consolidates the translated architectural and functional requirements needed to rebuild the legacy system in a modern stack.