🚚

Migration Plan Writer

Code & Development · by AIDiveForge · Apr 20, 2026 · Intermediate

Draft an incremental database migration plan with rollback gates from a before/after schema diff — no single-shot migrations that can't be reversed.

🧠 Why it works

The biggest outages from schema changes come from one-shot migrations that can't be rolled back once traffic hits the new code. Forcing the plan to decompose into independently-reversible phases eliminates the whole class of 'we have to forward-fix in prod' incidents.

⚙️ How it works

Parse both schemas into a normalized form (tables, columns, constraints, indices). 2. Classify each diff entry into one of: additive (always safe), destructive (needs a data migration), or transform (backfill). 3. Order phases so every destructive step is preceded by a deploy-new-code step that tolerates both old and new shapes. 4. For each phase, generate forward SQL + rollback SQL + a post-phase verification query that must return the expected row counts. 5. Annotate each phase with estimated lock time based on row count and table size.

Description

Input: two SQL schemas (or an ORM diff), plus an estimated row count for each affected table. Output: a numbered migration plan split into phases, each phase reversible independently, with a rollback script and a verification query for every phase.

Install this skill

A Claude skill is a skill.md file with YAML frontmatter and a markdown body. Drop the file into your tool of choice — or pick a different format if you use Cursor, Windsurf, Copilot, or something else.

Format Download skill.md

Quick install — paste into your terminal

mkdir -p ~/.claude/skills/migration-plan-writer \
  && curl -L https://aidiveforge.com/skill/migration-plan-writer.skill-md \
       -o ~/.claude/skills/migration-plan-writer/skill.md

Save to ~/.claude/skills/migration-plan-writer/skill.md

🧠 Why it works

⚙️ How it works

Description

Install this skill

Recommended Use

Report compatibility

Suggest a pairing