legacy-migration-planner

Generate evidence-based migration plans for legacy systems using the Strangler Fig pattern.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill legacy-migration-planner-rafael-hc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-migration-planner
Source: https://github.com/rafael-hc/AoPonto-FoodService/tree/main/.agents/skills/legacy-migration-planner
Command: npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill legacy-migration-planner-rafael-hc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured, evidence-based approach to planning complex system migrations, ensuring a clear roadmap and mitigating risks.

Core Features & Use Cases

  • Comprehensive Analysis: Deeply analyzes codebases, identifies bounded contexts, and researches technology stacks.
  • Risk Assessment: Maps technical, operational, and business risks with clear mitigation strategies.
  • Migration Roadmapping: Generates detailed per-domain migration plans and a consolidated roadmap using patterns like Strangler Fig.
  • Use Case: Planning the decomposition of a monolithic application into microservices, including identifying service boundaries, designing APIs, and creating a phased rollout strategy.

Quick Start

Use the legacy-migration-planner skill to analyze the current codebase and generate a migration plan.

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 migration from a monolith to microservices?

To plan a monolith to microservices migration, analyze codebases to identify bounded contexts, map dependencies, and generate per-domain plans. This approach uses structured methodologies like the Strangler Fig pattern to ensure a phased, risk-mitigated rollout.

What is the Strangler Fig pattern and when should I use it for system migration?

The Strangler Fig pattern is a migration strategy that gradually replaces legacy monolith components with new services. Use it to decompose systems safely by routing traffic to new bounded contexts incrementally, minimizing operational disruption during codebase modernization.

How do I identify bounded contexts before decomposing a legacy codebase?

Identifying bounded contexts requires deeply analyzing codebases and mapping dependencies to find logical domain boundaries. This evidence-based analysis separates business capabilities, forming the foundation for targeted per-domain migration plans and microservices design.

Can I use this approach to assess technical and business risks during a system modernization roadmap?

Yes, system modernization roadmapping includes mapping technical, operational, and business risks. The analysis generates clear mitigation strategies for each identified risk, ensuring the consolidation or decomposition plan proceeds with confidence.

What's the best way to create a phased rollout strategy for legacy system modernization?

The best way to create a phased rollout strategy is generating a consolidated roadmap using the Strangler Fig pattern. This involves researching target technology stacks, mapping domain dependencies, and sequencing per-domain migrations to mitigate risks.

When should I not use a microservices migration roadmap for refactoring?

Avoid a microservices migration roadmap if your legacy system lacks complex domain boundaries or if dependencies are too tightly coupled to separate safely. Without clear bounded contexts, decomposition introduces unnecessary operational risks and distributed system overhead.