plan-strangler-migration

Generate a step-by-step migration roadmap for legacy system modernization.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill plan-strangler-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-strangler-migration
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/plan-strangler-migration
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill plan-strangler-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the high-risk challenge of replacing or rewriting legacy system components without causing downtime or requiring a dangerous big-bang cutover.

Core Features & Use Cases

  • Behavioral Pinning: Uses golden-master testing to capture and preserve existing system behavior, including legacy quirks, before any changes are made.
  • Incremental Migration: Facilitates the strangler-fig pattern by routing traffic through seams, allowing for shadow testing, canary releases, and reversible rollbacks.
  • Use Case: When migrating a monolithic service to a microservice architecture, this skill provides the framework to carve out specific endpoints, verify parity on live traffic, and safely flip the default implementation.

Quick Start

Use the plan-strangler-migration skill to generate a step-by-step migration roadmap for replacing the legacy payment module with a new service while maintaining full rollback capability.

Frequently Asked Questions about plan-strangler-migration

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

FAQPage Schema
How do I migrate a monolith to microservices with zero downtime?

Incremental modernization using the strangler-fig pattern routes traffic through seams, enabling shadow testing and reversible rollbacks to ensure zero-downtime transitions. It safely carves out specific endpoints to verify parity on live traffic before flipping the default implementation.

What is the best way to preserve legacy system behavior during a framework upgrade?

Behavioral pinning uses golden-master testing to capture and preserve existing system behavior, including legacy quirks, before any changes are made. This characterization testing maintains system parity and safety throughout the incremental migration process.

How do I decompose a god-class without causing a dangerous big-bang cutover?

Decomposing a god-class incrementally requires implementing characterization tests, traffic shadowing, and expand-contract data migration strategies. This approach replaces components safely by routing traffic through seams, avoiding a dangerous big-bang cutover.

Can I roll back a new service if traffic shadowing reveals parity issues?

Yes, the incremental migration process facilitates canary releases and reversible rollbacks. By routing live traffic through seams to shadow test the new implementation, you can safely revert to the legacy system if parity issues are detected.

When should I use the strangler-fig pattern instead of a full system rewrite?

Use the strangler-fig pattern when replacing legacy system components carries high risk and requires zero downtime. It provides a step-by-step migration roadmap to incrementally extract services, avoiding the dangers of a big-bang cutover.