reversa-migrate

You can orchestrate a multi-agent migration workflow by running /reversa-migrate, which coordinates six specialized agents to transform legacy Reversa specs into a modern, codable architecture with human-in-the-loop pauses.

Managing handoffs during a code migration is handled by a six-agent pipeline that validates required artifacts, maintains migration state, and produces a final handoff.md file to ensure a clean transition to the coding phase.

Yes, you can automate the migration pipeline without manual pauses by enabling the optional auto mode, which applies defaults and runs the six-agent migration flow continuously without human-in-the-loop interruptions.

Artifact validation during a legacy specification migration works by checking required artifacts against the legacy set, maintaining artifact hashes, and managing strict state in the _reversa_sdd/migration directory to ensure consistency.

No external dependencies are required to run the Reversa migration workflow, as the orchestration operates independently to coordinate the six specialized agents and manage the migration state.

You should use a multi-agent pipeline for design migration when you need to translate complex legacy specifications into a modern architecture, requiring distinct phases like strategy, design, and inspection with strict artifact validation.