reversa-migrate

Orchestrates migration of legacy discovery artifacts into rebuild-ready specifications with resumable state and handoff generation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts legacy system discovery outputs into modern, rebuild-ready migration specifications by orchestrating a structured multi-agent pipeline.

Core Features & Use Cases

  • Migration orchestration: Coordinates the full migration workflow after /reversa has populated _reversa_sdd/, ensuring the right sequence of specialized agents.
  • Spec-driven transformation: Operates only on already-produced specs in _reversa_sdd/ (no legacy code touching and no schema archaeology).
  • Human approval checkpoints: Enforces interactive decision gates for topology and screen modernization so critical choices are not silently assumed.
  • Stateful resumability: Uses _reversa_sdd/migration/.state.json to support --resume, checkpointing, and phase-aware regeneration.
  • Handoff package generation: Produces _reversa_sdd/migration/handoff.md with artifacts, required reading order, and coding next steps.

Quick Start

Run re-reversa first, then start the orchestrated migration by asking the AI to execute /reversa-migrate with your desired mode (interactive or --auto).

Frequently Asked Questions about reversa-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert legacy system discovery artifacts into rebuild-ready specifications?

Legacy spec migration transforms discovery artifacts into modern rebuild-ready specifications by orchestrating a structured multi-agent pipeline with phase checkpoints, state management, and human approval gates for topology and screen modernization decisions.

What is the best way to orchestrate a multi-agent migration workflow with human approval gates?

Multi-agent migration orchestration coordinates specialized agents sequentially across phases, enforcing interactive decision gates for topology and screen modernization so critical choices require explicit human approval rather than silent assumptions.

How do I resume an interrupted legacy spec migration without losing progress?

Resuming an interrupted legacy spec migration uses `_reversa_sdd/migration/.state.json` to support `--resume`, checkpointing progress and enabling phase-aware regeneration so you can continue from the last completed stage without data loss.

Do I need to run legacy code discovery before starting a spec-driven migration pipeline?

Yes, spec-driven migration requires running `/reversa` first to populate `_reversa_sdd/` with discovery artifacts, as the migration pipeline operates only on already-produced specs without touching legacy code or performing schema archaeology.

What does a migration handoff package include for code rebuild planning?

A migration handoff package includes `_reversa_sdd/migration/handoff.md` containing consolidated artifacts, required reading order, ambiguity handling, and coding next steps to guide the downstream rebuild implementation.

Can I automate the migration pipeline without interactive decision checkpoints?

Yes, the migration pipeline supports `--auto` mode to bypass interactive checkpoints, though human approval gates for topology and screen modernization exist to ensure critical architectural choices are not silently assumed during automated execution.