reversa-migrate

Migration workflow orchestration coordinates six specialized agents sequentially, inserting human-in-the-loop pauses to validate artifacts and manage state. It ultimately generates a consolidated handoff document for coders to execute the system migration.

State management during a system migration pipeline tracks sequential agent decisions and artifacts within a structured directory. This enables workflows to resume, regenerate outputs, or run automatically without losing prior migration context.

Populated legacy specifications are required before starting an automated migration. The orchestrator cannot collect briefs or invoke sequential agents until legacy discovery populates the designated directory with the necessary initial artifacts.

Generating a handoff document for coders occurs after six sequential migration agents complete their assessments. The orchestrator consolidates validated artifacts and human-in-the-loop decisions into a structured markdown file for downstream coding.

Running a migration pipeline in auto mode bypasses human-in-the-loop pauses, executing the six sequential agents continuously. State management and artifact validation still operate normally, allowing automatic generation of the final handoff document.

Migration workflow orchestration may fail to resume if the structured state management directory is missing or corrupted. The pipeline relies on these stored artifacts and decision logs to validate previous steps and regenerate the workflow context correctly.