role-architect:migration-planner

Plan system migrations using Strangler Fig, parallel runs, and zero-downtime methods.

14|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rnavarych/alpha-engineer --skill role-architect-migration-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-architect:migration-planner
Source: https://github.com/rnavarych/alpha-engineer/tree/main/plugins/roles/role-architect/skills/migration-planner
Command: npx skills add https://github.com/rnavarych/alpha-engineer --skill role-architect-migration-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance and strategies for planning and executing complex system migrations, minimizing risk and downtime.

Core Features & Use Cases

  • Migration Strategy: Offers expertise on patterns like Strangler Fig and parallel runs.
  • Data Migration: Details techniques such as ETL, CDC, and dual-write.
  • Zero-Downtime: Explains methods like blue-green deployments and expand-and-contract schema changes.
  • Use Case: Planning an incremental migration from a monolithic legacy system to a microservices architecture using the Strangler Fig pattern, ensuring data consistency and minimal user disruption.

Quick Start

Use the migration planner skill to outline a strangler fig migration strategy for replacing a legacy user authentication service.

Frequently Asked Questions about role-architect:migration-planner

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

FAQPage Schema
How do I plan a zero downtime migration from a monolith to microservices?

Ensure data consistency during system migration by employing techniques like Change Data Capture (CDC), dual-write, or ETL processes. These methods synchronize data between legacy and new systems in real-time or batch, preventing loss during the transition.

What is the Strangler Fig pattern for incremental system replacement?

Implement rollback plans and risk mitigation by defining clear phased timelines and feature parity tracking. Establishing criteria for reverting to the legacy system if migration milestones fail ensures safe, controlled incremental system replacements.

How does expand-and-contract schema change work for zero downtime deployments?

Yes, this migration planner handles feature parity tracking by providing structured methodologies to map and compare legacy system behaviors against new implementations. It ensures functional equivalence before fully transitioning user traffic.

What is the best way to execute parallel runs during a system migration?

The best way to execute parallel runs is to route duplicated traffic to both legacy and new systems simultaneously, comparing outputs for consistency. This validation strategy builds confidence before fully cutting over to the replacement architecture.