migration-plan

Develop phased migration plans for databases, services, and frameworks.

1|Updated Mar 6, 2026

Search Tags:#rollback #database #migration #service #feature flags #strangler fig

Ready to run

npx skills add https://github.com/chavangorakh1999/sde-skills --skill migration-plan-chavangorakh1999

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-plan
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-architecture/skills/migration-plan
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill migration-plan-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you plan and execute complex migrations (databases, services, languages) safely, minimizing downtime and risk by employing strategies like the Strangler Fig pattern and feature flags.

Core Features & Use Cases

Phased Rollout Strategy: Defines clear phases from preparation to cleanup.
Rollback Planning: Establishes triggers and procedures for instant reversibility.
Data Migration Guidance: Provides patterns for zero-downtime database changes.
Use Case: Planning to migrate your monolithic user service to a new microservice architecture? Use this Skill to outline the phased rollout, dual-write strategy, and rollback plan.

Quick Start

Use the migration-plan skill to plan a database migration from PostgreSQL to MySQL.

Frequently Asked Questions about migration-plan

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

FAQPage Schema

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

A safe database migration requires a phased rollout strategy that establishes clear preparation, dual-write, and cleanup phases to ensure zero-downtime transitions while maintaining data integrity.

What is the Strangler Fig pattern for service migration?▼

The Strangler Fig pattern for service migration involves gradually replacing a monolithic system by building new microservices alongside the old one, routing traffic incrementally until the legacy service is fully decommissioned.

How do you define rollback triggers for a phased migration?▼

Defining rollback triggers for a phased migration involves establishing specific monitoring thresholds and error conditions that automatically initiate instant reversibility procedures to switch traffic back to the stable legacy system.

Can I use feature flags for dark launching a new microservice?▼

Yes, you can use feature flags for dark launching a new microservice by routing test traffic to the new service while keeping production traffic on the old system, allowing validation without impacting end users.

What is the best way to migrate a monolithic user service to microservices?▼

The best way to migrate a monolithic user service to microservices is employing a phased rollout strategy using the Strangler Fig pattern, dual-write data synchronization, and defined rollback procedures to ensure a safe transition.