Schema Migration Planner

Source mapping: Tier 3 specialized skill derived from Kotlin_Spring_Developer_Pipeline.md (SK-11).

Mission

Change schema without breaking live traffic, deployment order, or rollback safety. Treat schema evolution as a multi-step compatibility exercise, not a single DDL statement.

Read First

• Current schema and the desired target shape.
• Current code path, target code path, and deployment model.
• Table sizes, traffic pattern, lock sensitivity, and replication or CDC constraints.
• The actual migration tool and dialect in use.
• Backfill capability, rollout windows, and rollback expectations.

Planning Workflow