Migration Planner
Plan safe, zero-downtime migrations for schemas, services, and infrastructure
Best use case
Migration Planner is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Plan safe, zero-downtime migrations for schemas, services, and infrastructure
Teams using Migration Planner should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/migration-planner/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Migration Planner Compares
| Feature / Agent | Migration Planner | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Plan safe, zero-downtime migrations for schemas, services, and infrastructure
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Migration Planner Skill Plan safe, zero-downtime migrations for schemas, services, and infrastructure. ## Trigger Conditions - Schema migration files are created or modified - A service migration or infrastructure change is planned - User invokes with "plan migration" or "migration strategy" ## Input Contract - **Required:** Current state (schema, service, infrastructure) - **Required:** Target state (desired end state) - **Optional:** Constraints (downtime window, data volume, timeline) ## Output Contract - Phased migration plan with rollback steps - Risk assessment per phase - Data validation checkpoints - Estimated duration and resource requirements ## Tool Permissions - **Read:** Schema files, migration history, service configs - **Write:** Migration plan documents, migration scripts - **Execute:** Schema comparison tools ## Execution Steps 1. Analyze current and target state; identify delta 2. Decompose into phases using expand-and-contract pattern 3. Identify backward-compatibility requirements per phase 4. Design rollback procedure for each phase 5. Estimate data volume and migration duration 6. Create validation checkpoints between phases 7. Document the plan with risk scores ## Success Criteria - Every phase is independently rollback-able - No phase requires downtime - Data validation checkpoints defined between phases - Risk assessment includes worst-case scenarios ## Escalation Rules - Escalate if migration affects >100M rows - Escalate if cross-service coordination is required - Escalate if estimated lock time exceeds 30 seconds ## Example Invocations **Input:** "Rename the users.email column to users.email_address" **Output:** 3-phase plan: Phase 1 (add email_address column, backfill, dual-write), Phase 2 (switch readers to email_address, verify), Phase 3 (drop email column). Estimated: 2 deploys, 45min backfill on 5M rows. Rollback at each phase documented.
Related Skills
claude-opus-4-5-migration
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.
airflow-3x-migration
Comprehensive guide and patterns for migrating Apache Airflow 2.x workflows to Airflow 3.x, covering import changes, deprecated features, and new paradigms like Asset scheduling and TaskFlow API.
Adaptive Daily Reflection & Planner
An intelligent daily check-in assistant that adapts its depth based on user engagement. It collects key activities and emotions for daily summaries while extracting tasks for to-do list management.
tuist-migration
Integrates Tuist into an existing iOS project that uses SPM local packages. Use when migrating a project from a manually maintained .xcodeproj to a Tuist-generated project, adding Tuist as an orchestration layer on top of SPM. Covers 8 sequential phases — audit, base structure, helpers, generation, schemes, CI, cache, and validation. Includes automation scripts and AI prompt templates for each phase.
molt-planner
MoltPlanner is a Google Calendar integration skill enabling agents to collaborate with users for interactive event scheduling and management.
seo-content-planner
Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.
wave-planner
Transform project issues into execution-ready implementation plans with risk prediction, wave-based organization, specialist agents, and TDD workflow
Schema Migration
Create safe, zero-downtime schema migrations with rollback procedures
planner
Generate staged project plans from design through deployment. Use when planning App Platform projects, breaking complex deployments into resumable stages, or tracking multi-step infrastructure setup.
database-migrations-sql-migrations
SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, SQL Server
database-migration
Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data tr...
apply-migration
Apply SQL migration files to JusticeHub Supabase database with verification and error handling.