migration-planner

Plan phased data and system migrations with rollback and validation checks.

5|Updated Dec 31, 2025

Search Tags:#rollback #validation #migration #zero-downtime #feature-flag #data-migration #dual-write

Ready to run

npx skills add https://github.com/patricio0312rev/skillset --skill migration-planner-patricio0312rev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-planner
Source: https://github.com/patricio0312rev/skillset/tree/main/templates/architecture/migration-planner
Command: npx skills add https://github.com/patricio0312rev/skillset --skill migration-planner-patricio0312rev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating large-scale migrations (data, databases, or platforms) without downtime or risk, by providing structured phased plans, rollback strategies, and validation checks.

Core Features & Use Cases

Feature-flag driven migrations enabling controlled rollout and immediate rollback if needed.
Dual-write and backfill workflows to keep old and new systems synchronized during transition.
Comprehensive validation, monitoring, and rollback plans to ensure data integrity and minimize downtime.
Flexible templates for data, schema, or platform migrations that adapt to different environments.
Risk mitigation, communication plans, and stakeholder alignment throughout the migration.

Quick Start

Provide a phased migration plan for a data, database, or platform migration using feature flags, dual writes, backfills, and validation.

Frequently Asked Questions about migration-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan a zero-downtime database migration?▼

A zero-downtime database migration requires a phased plan using dual-write workflows and feature flags to synchronize old and new systems. This approach includes backfilling data, running validation checks, and preparing rollback strategies to ensure data integrity without service interruption.

What is dual-write and backfill in data migrations?▼

Dual-write and backfill in data migrations keep old and new systems synchronized during transition. Dual-write captures new writes to both systems simultaneously, while backfill populates the new system with existing data, ensuring consistency before the final cutover.

How do I use feature flags for controlled migration rollouts?▼

Feature flags enable controlled migration rollouts by routing traffic to the new system incrementally. This allows immediate rollback if issues arise, minimizing risk and providing validation monitoring before fully decommissioning the legacy platform.

Can I use this for schema changes and platform upgrades?▼

Yes, you can use this for schema changes and platform upgrades. It provides flexible templates that adapt to different environments, supporting phased decommissioning, risk mitigation, and stakeholder alignment for complex infrastructure transitions.

What is the best way to create a rollback plan for data migrations?▼

The best way to create a rollback plan for data migrations involves feature-flag driven deployment and dual-write synchronization. This setup allows you to instantly revert traffic to the original system while maintaining data integrity through continuous validation checks.

When do I need a phased decommissioning plan for complex environments?▼

You need a phased decommissioning plan for complex environments when coordinating large-scale data, database, or platform migrations without downtime. It ensures structured risk mitigation, validation, and stakeholder alignment throughout the entire transition lifecycle.