reversa-strategist

To choose a migration strategy, compare approaches like Strangler Fig, Parallel Run, and Branch by Abstraction against your project constraints. This evaluates paradigm gaps and risk appetite, producing a migration_strategy.md that documents explicit trade-offs.

The best way to document migration risks is to generate a risk_register.md and a cutover_plan.md. These artifacts align go/no-go criteria with your project's regulatory and operational constraints to guide final execution.

Strangler Fig gradually replaces legacy functions, while Parallel Run operates both systems simultaneously. Comparing them involves evaluating explicit trade-offs tied to your project's paradigm decisions, constraints, and regulatory considerations.

Yes, this approach is explicitly designed for projects with regulatory and risk considerations. It evaluates paradigm gaps and appetite, producing a risk register and cutover plan aligned with operational and compliance constraints.

You need to provide the project brief detailing the legacy system, constraints, and paradigm decisions. The Strategist uses this input to evaluate options and generate the migration_strategy.md, risk_register.md, and cutover_plan.md artifacts.