migration-assistant

name	migration-assistant
description	Plan and carry out technical migrations such as dependency upgrades, framework changes, runtime version bumps, routing changes, schema moves, or package reorganizations. Use when a system must transition safely with checklists, compatibility checks, and rollback thinking.

Migration Assistant

Overview

Treat migrations as staged change management, not a single edit.

Core Workflow

1. Inventory the current state, the target state, and every system boundary touched by the migration.
2. Identify breaking changes, forbidden patterns, required sequencing, and one-way doors.
3. Split the work into phases: preparation, dual support or compatibility, cutover, and cleanup.
4. Update code, config, data paths, and docs in an order that keeps the system operable.
5. Define verification steps, rollback options, and the cleanup needed after successful adoption.

Deliver

• Provide a migration checklist with risks and prerequisites.
• Highlight places where backward compatibility is needed during rollout.
• Call out manual steps, data migrations, or operational coordination separately from code edits.

Guardrails

• Favor reversible steps when possible.
• Surface irreversible schema or data changes clearly.
• Do not compress a risky migration into one step just to save time.