skills.rest
cliffthelin
cliffthelinCOMMUNITY
Explore all skills by this author →
GitHub

reversa-migrate

Orchestrate a six-agent Reversa migration pipeline to produce handoff.md artifacts.

Updated May 13, 2026
Search Tags:#agent workflow#intent resolution#migration orchestration#human approval checkpoints#reversa#policy-driven development#spec-to-code handoff
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-migrate-cliffthelin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-migrate
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/skills/reversa/reversa-migrate
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-migrate-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill orchestrates the Reversa Migration Team so your legacy-system findings (already discovered by /reversa) can be transformed into migration-ready specifications and a final coding handoff.

Core Features & Use Cases

  • Pipeline orchestration: Runs the 6 migration agents in order (Paradigm Advisor → Curator → Strategist → Designer → Screen Translator → Inspector) to produce a complete set of migration artifacts.
  • Spec-driven migration only: Uses outputs from _reversa_sdd/ and does not touch legacy source code or perform archaeology.
  • Safety rails and checkpoints: Enforces prerequisites, validates required artifacts, supports resume, and uses human pauses/approvals when decisions are needed.

Quick Start

Use the /reversa-migrate skill after you have run /reversa and generated _reversa_sdd/, then enter /reversa-migrate to start the migration interview and agent pipeline.

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 workflow using spec-driven development?▼

Legacy system migration orchestration runs a six-agent pipeline to transform existing discovery specifications into migration-ready artifacts. It executes agents sequentially, producing a final coding handoff document without touching legacy source code.

What is a migration handoff in spec-to-code workflows?▼

A migration handoff is a generated document containing finalized specifications derived from legacy system discovery. It acts as the transfer point where migration-ready artifacts are passed from the planning pipeline to coding teams for implementation.

How do I add human approval checkpoints to an automated migration pipeline?▼

Human approval checkpoints are integrated into the migration pipeline using state tracking. The workflow pauses execution to require manual validation at key decision points, recording state in a dedicated JSON file before resuming the agent sequence.

Do I need to run a full system discovery phase before starting spec-to-code migration?▼

Yes, spec-to-code migration requires a completed discovery phase. The workflow strictly depends on a populated specification directory and validates expected required artifacts against a reference YAML file before initiating the migration agents.

Can I resume a migration pipeline if an agent sequence fails during execution?▼

The migration pipeline supports resuming execution after interruptions. By tracking state through a JSON file within the specification directory, the workflow can recover and continue from the last completed human approval checkpoint or agent step.

What are the limitations of using spec-driven migration orchestration for legacy systems?▼

Spec-driven migration orchestration is limited to processing pre-existing discovery artifacts and cannot perform source code archaeology. It strictly requires populated specification directories and will fail precondition checks if expected artifacts are missing.

Related Skills

Explore More Software Engineering Skills→
afsjrafsjr

reversa-migrate

Orchestrate the Reversa migration pipeline from legacy specs to handoff.md.

Community
Advanced
sandecosandeco
1.5k

reversa-migrate

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

Community
Advanced
chieflatifchieflatif

notion

Define canonical Notion database schemas and read/write operations for SalesSidekick.

Community
Advanced
paritytechparitytech
8

migrating-to-product-sdk

Detect legacy product codebases and write migration specs for @parity/product-sdk.

Official
Advanced