Write Safe Migrations

Quick Start

Default approach: expand → migrate → contract.

Goal: reduce lock time, keep rollback easy, and prove correctness with checks.

When to use this skill

• any production schema change (especially large tables)
• adding columns/indexes/constraints, renames, backfills, or data moves
• when rollback must be possible without restoring from backup

Before you start (inputs)