reversa-migrate

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It coordinates the Reversa migration pipeline that converts legacy system specs into modern, reconstruction-ready specifications, ensuring the required discovery artifacts exist before proceeding.

Core Features & Use Cases

  • Migration orchestration across 6 agents: runs the Paradigm Advisor → Curator → Strategist → Designer → Screen Translator → Inspector sequence to produce the full migration spec set.
  • Safety-first gating and resumability: verifies the presence of expected legacy artifacts in _reversa_sdd/, manages checkpoints via .state.json, and supports --resume to continue after interruptions.
  • Human approval checkpoints: enforces interactive approval for Designer topology/architecture and Screen Translator mode/generation decisions, or applies controlled defaults via --auto.
  • Production handoff: consolidates ambiguity and generates handoff.md for the coding agent, clearly highlighting the required reading order and pending blockers.

Quick Start

Use reversa-migrate to orchestrate migration after discovery by running /reversa first, then invoke /reversa-migrate to generate migration specs and a coding handoff.

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 from spec transformation to handoff generation?

Legacy system migration orchestration runs six specialized agents sequentially with checkpointed execution to transform specs in _reversa_sdd/ into migration-ready artifacts. It validates expected legacy artifacts, manages progress via state file checkpoints, and produces a final handoff document for implementation.

What is spec transformation in the context of legacy modernization workflows?

Spec transformation in legacy modernization converts existing system specifications into modern, reconstruction-ready specifications. This process uses a pipeline of specialized agents, including a Paradigm Advisor, Curator, and Strategist, to analyze and update legacy artifacts for migration.

How do I resume an interrupted migration pipeline with checkpointing?

To resume an interrupted migration pipeline with checkpointing, use the --resume flag. The orchestration process persists progress in a state file, allowing the migration to continue from the last checkpoint without restarting the entire agent sequence.

Can I automate human approval gating for migration orchestration?

Yes, you can automate human approval gating for migration orchestration using the --auto flag. This applies controlled defaults for the Designer and Screen Translator phases, bypassing interactive approval gates to streamline the pipeline execution.

Do I need to validate expected legacy artifacts before running a migration pipeline?

Yes, you need to validate expected legacy artifacts before running a migration pipeline. The orchestration verifies the presence of expected legacy artifacts in the _reversa_sdd/ directory to ensure the required discovery artifacts exist before proceeding with the migration.

What's the best way to consolidate ambiguity for a coding handoff in legacy modernization?

The best way to consolidate ambiguity for a coding handoff in legacy modernization is to generate a handoff document that highlights the required reading order and pending blockers. This ensures the coding agent has clear context and understands unresolved issues.