legacy-migration-planner

Analyze codebases and generate phased migration plans using the Strangler Fig pattern.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/P4rzi/PROT-RISK --skill legacy-migration-planner-p4rzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-migration-planner
Source: https://github.com/P4rzi/PROT-RISK/tree/main/.github/skills/legacy-migration-planner
Command: npx skills add https://github.com/P4rzi/PROT-RISK --skill legacy-migration-planner-p4rzi

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 software system migrations, reducing risk and ensuring a clear roadmap for modernization.

Core Features & Use Cases

  • Comprehensive Analysis: Deeply analyzes codebases, identifies bounded contexts, and researches technology stacks.
  • Risk Assessment: Maps and scores technical, operational, and business risks associated with migration.
  • Strategic Planning: Designs migration strategies (e.g., Strangler Fig pattern), defines seams, and creates per-domain and consolidated roadmaps.
  • Use Case: Planning to migrate a monolithic e-commerce platform to microservices? This Skill will analyze your current codebase, identify logical domains, research target technologies, assess risks, and generate a phased migration plan using the Strangler Fig pattern.

Quick Start

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

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 using the Strangler Fig pattern?

To plan a monolith to microservices migration, this Skill analyzes your codebase to identify bounded contexts and domain seams, assesses technical risks, and generates a phased Strangler Fig pattern roadmap for incremental decomposition.

What is codebase analysis for legacy system modernization?

Codebase analysis for legacy modernization is the process of deeply examining existing source code to map bounded contexts, identify logical domains, and research target technology stacks for a structured architectural refactoring.

Can I use this to plan a cross-language rewrite and framework upgrade?

Yes, you can use this Skill to plan cross-language rewrites and framework upgrades. It supports various migration directions by researching target stacks, evaluating operational risks, and designing actionable modernization roadmaps.

Does legacy migration require a risk assessment before decomposition?

Yes, legacy migration requires a risk assessment before decomposition. This Skill maps and scores technical, operational, and business risks associated with the refactoring to ensure a structured and confident migration strategy.

What's the best way to consolidate microservices back into a unified architecture?

The best way to consolidate microservices is to analyze the current distributed codebase, map domain boundaries, assess integration risks, and generate a consolidated roadmap using proven migration methodologies like the Strangler Fig pattern.

When should I not use a Strangler Fig pattern for refactoring?

You should reconsider the Strangler Fig pattern if your codebase analysis reveals tightly coupled domains without clear seams, making incremental replacement infeasible without high operational and business risk during the migration.