legacy-migration-planner

Generates evidence-based legacy system migration plans using the Strangler Fig pattern.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Peterson-Benhame/agent-skills --skill legacy-migration-planner-peterson-benhame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-migration-planner
Source: https://github.com/Peterson-Benhame/agent-skills/tree/main/packages/skills-catalog/skills/%28architecture%29/legacy-migration-planner
Command: npx skills add https://github.com/Peterson-Benhame/agent-skills --skill legacy-migration-planner-peterson-benhame

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Planning a legacy system migration without a structured, evidence-based approach leads to missed dependencies, broken integrations, and failed cutovers. This Skill produces comprehensive migration plans grounded in actual codebase analysis and verified external research, covering monolith decomposition, microservices consolidation, cross-language rewrites, and framework upgrades. ## Core Features & Use Cases - Two-Phase Methodology: A mandatory RESEARCH phase (codebase analysis, domain mapping, stack research, risk assessment) followed by a PLAN phase (seam design, per-domain migration files, consolidated roadmap). - Strangler Fig Pattern Library: Six proven patterns including API Gateway Strangler, Database Dual-Write, UI Component Strangler, and Branch by Abstraction, with phased traffic rollout and rollback triggers. - Testing Safety Nets: Characterization tests, contract tests, parallel runs, and data consistency validation mapped to each migration phase. - Use Case: You need to decompose a Node.js monolith into microservices. The Skill analyzes your codebase with file:line citations, identifies bounded contexts with coupling scores, researches current stack versions via web search, and outputs a phased roadmap with per-domain migration plans, rollback strategies, and risk mitigations. ## Quick Start Ask the agent to analyze this codebase and produce a legacy migration plan using the Strangler Fig pattern, starting with the research phase.

Frequently Asked Questions about legacy-migration-planner

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

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

Start with a research phase that maps modules, identifies bounded contexts via coupling analysis, and catalogs integration points with file:line references. Then design seams and facades, write per-domain migration plans, and sequence domains by dependency order using the Strangler Fig pattern.

What is the Strangler Fig pattern for legacy migration?

The Strangler Fig pattern gradually replaces a legacy system by routing traffic between old and new implementations through a facade or gateway. It uses phased rollouts (shadow, canary, ramp, full) with defined validation criteria and instant rollback via feature flags.

Can this skill handle microservices to monolith consolidation?

Yes, the skill is direction-agnostic and covers consolidation, cross-language rewrites, framework upgrades, and frontend migrations. The migration direction is determined by evidence from the research phase, not assumed upfront.

Does the migration planner write implementation code?

No, it produces plans only, not implementation code. Output consists of research documents, per-domain migration files, and a consolidated roadmap that other agents or developers execute.

What testing strategies protect a database migration?

Use the Database Strangler dual-write pattern with continuous data consistency validation: row count comparison, random sample checks, and reconciliation jobs. Contract tests and parallel runs verify behavioral parity before traffic switches.

When should I not use this migration planning skill?

Do not use it for domain analysis, component sizing, or step-by-step decomposition planning, which are handled by dedicated skills. It is also unsuitable when you need actual code implementation rather than a migration plan.