/migrate Migration Workflow Safe migrations for frameworks, languages, and infrastructure. When to Use "Migrate to X" "Upgrade framework" "Move from X to Y" "Upgrade Python/Node/etc." "Migrate database" Framework version upgrades Language migrations Infrastructure changes Workflow Overview Agent Sequence Agent Role Output 1 oracle Research target framework/version Research report 2 phoenix Analyze current codebase for migration impact Impact analysis 3 plan agent Create phased migration plan Migration plan 4 kraken Implement migration changes Code changes 5 surveyor Review migration for completeness Migration review Why Extra Gates? Migrations are high risk: Breaking changes between versions Dependency conflicts Data format changes API deprecations The extra research and review phases catch issues early. Execution Phase 1: Research Target Phase 2: Analyze Current State Phase 3: Plan Migration Phase 4: Implement Phase 5: Review Migration Migration Types Framework Upgrade Language Version Database Migration Infrastructure Example Incremental Migration For large codebases, run one phase at a time: Flags phase N : Run specific phase only dry run : Plan without implementing rollback : Execute rollback plan parallel : Run new alongside old (strangler fig)