reversa-migrate

Run six migration agents to transform legacy specs into build-ready artifacts.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-migrate-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-migrate
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-migrate
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-migrate-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill coordinates a safe, end-to-end migration pipeline in the Reversa workflow, turning legacy specs already discovered and populated into a complete set of modern, build-ready migration artifacts.

Core Features & Use Cases

  • Pre-flight validation of discovery outputs: Blocks the migration if required artifacts under _reversa_sdd/ are missing, and instructs the user to run /reversa first.
  • Six-agent migration orchestration: Runs Paradigm Advisor, Curator, Strategist, Designer, Screen Translator, and Inspector in the correct sequence, including checkpointing phases that require human approval.
  • Stateful resume and destructive regeneration controls: Supports --resume, --regenerate (by agent/phase), and --auto (with explicit defaults) while persisting progress in _reversa_sdd/migration/.state.json.
  • Human-in-the-loop decision gates: Uses pending decisions and pauses before proceeding, then consolidates ambiguity outcomes into ambiguity_log.md and produces handoff.md for the coding agent.

Quick Start

Run reversa first to generate _reversa_sdd/, then activate reversa-migrate to produce _reversa_sdd/migration/ artifacts and a final handoff for the coding agent.

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 with human approval gates?

Legacy system migration orchestration with human approval gates is handled by running six specialized migration agents in sequence, pausing at Designer and Screen Translator phases to require explicit human approval before proceeding to final artifact consolidation.

What is the best way to transform legacy specs into modern build-ready migration artifacts?

Transforming legacy specs into modern stack-ready migration specifications requires validating discovered artifacts in _reversa_sdd/ first, then executing a six-agent pipeline that outputs a complete set of build-ready migration artifacts and a final handoff document.

Do I need to run discovery before migrating legacy system specifications?

Yes, legacy system specification migration requires running discovery first to populate the _reversa_sdd/ directory. Pre-flight validation blocks the migration pipeline if required artifacts are missing and instructs you to run the discovery phase beforehand.

Can I resume a migration pipeline if it stops at a human approval gate?

Yes, you can resume a migration pipeline using the --resume flag, which reads strict state handling data from _reversa_sdd/migration/.state.json to continue paused phases, or use --regenerate to rerun specific agents.

How does state management work during a multi-agent spec transformation pipeline?

State management during spec transformation pipelines persists progress in _reversa_sdd/migration/.state.json, enabling stateful resume, destructive regeneration by agent phase, and automated mode with explicit defaults while tracking pending decisions and checkpoint phases.

What artifacts are generated after orchestrating a complete legacy migration sequence?

Orchestrating a complete legacy migration sequence generates modern migration specifications in _reversa_sdd/migration/, including an ambiguity_log.md consolidating pending decisions and a handoff.md providing build-ready instructions for the coding agent.