migration-refactor-specialist

Plan phased migrations and refactors for legacy systems with rollback criteria.

22|6|Updated Mar 10, 2026

Search Tags:#migrations #risk-management #rollout #legacy-modernization #upgrade-planning #refactors

Ready to run

npx skills add https://github.com/felvieira/claude-skills-fv --skill migration-refactor-specialist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-refactor-specialist
Source: https://github.com/felvieira/claude-skills-fv/tree/main/skills/23-migration-refactor-specialist
Command: npx skills add https://github.com/felvieira/claude-skills-fv --skill migration-refactor-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrations and refactors of large legacy systems are risky and complex; this skill guides teams to plan and execute upgrades with incremental rollout, explicit compatibility, and clear handoffs.

Core Features & Use Cases

Incremental migration planning: break large upgrades into safe phases with defined milestones and rollback criteria.
Risk-aware governance: explicit compatibility strategies, validation steps per phase, and staged handoffs to Orchestrator, Backend, Frontend, QA and Deploy.
Legacy modernization strategy: supports strangler pattern, component extraction, and safe transition paths for evolving architectures.

Quick Start

Provide a phased migration plan for a legacy module with incremental rollout and rollback criteria.

Frequently Asked Questions about migration-refactor-specialist

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

FAQPage Schema

How do I plan a safe legacy system migration with rollback criteria?▼

Plan safe legacy system migrations by breaking large upgrades into incremental phases with defined milestones, explicit compatibility strategies, and rollback criteria. This approach minimizes risk and provides clear validation steps before proceeding to the next rollout phase.

What is the strangler pattern for legacy modernization?▼

The strangler pattern is a legacy modernization strategy that incrementally replaces old system components by extracting them into new implementations. It enables safe transition paths while maintaining system functionality throughout the architecture evolution.

How do I break a large framework upgrade into safe incremental phases?▼

Break large framework upgrades into safe incremental phases by defining phased milestones, risk assessments, and staged handoffs to Orchestrator, Backend, Frontend, QA and Deploy. Each phase requires explicit validation steps and rollback criteria before advancing.

Can I use incremental rollout for architecture changes in large systems?▼

Yes, incremental rollout supports architecture changes in large systems by applying component extraction and the strangler pattern. This ensures safe transitions with explicit compatibility strategies and structured risk-aware governance throughout the migration lifecycle.

What's the best way to manage risk during a legacy refactor?▼

Manage legacy refactor risks through risk-aware governance that enforces explicit compatibility strategies, validation steps per phase, and staged handoffs. This structured approach ensures safe incremental migration planning and clear deliverables for downstream teams.