Skip to content
Back to skills

Migration Planner

ASecurity

Plan safe, zero-downtime migrations for schemas, services, and infrastructure

  • 57 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
databasesgodatabase

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill migration-planner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Migration Planner?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Migration Planner
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-migration-planner/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-migration-planner)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Migration Planner
description: Plan safe, zero-downtime migrations for schemas, services, and infrastructure
category: database
version: 1.0.0
triggers:
  - schema-migration
  - service-migration
  - infrastructure-migration
globs: "**/migrations/**,**/infrastructure/**"
---

# 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.