refactoring-mikado-strangler

Plan incremental large-scale refactors using Mikado and Strangler Fig.

41|7|Updated Jan 30, 2026

Search Tags:#refactoring #code-quality #incremental #strangler-fig #architecture-migration #mikado

Ready to run

npx skills add https://github.com/DGouron/review-flow --skill refactoring-mikado-strangler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactoring-mikado-strangler
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/refactoring
Command: npx skills add https://github.com/DGouron/review-flow --skill refactoring-mikado-strangler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large-scale refactors are risky, error-prone, and difficult to coordinate across teams.

Core Features & Use Cases

Structured guidance for architecture migrations using Mikado and Strangler Fig to map dependencies and enable incremental changes.
Supports safe co-existence of old and new systems with explicit tracking and planning artifacts.

Quick Start

Outline the current architecture and generate the Mikado graph and Strangler plan to begin incremental migration.

Frequently Asked Questions about refactoring-mikado-strangler

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

FAQPage Schema

How do I plan a large-scale architecture migration safely?▼

Use the Mikado method to map code dependencies incrementally and the Strangler Fig pattern to execute staged architecture migrations while maintaining functional parity between old and new systems.

What is the Mikado method for refactoring?▼

The Mikado method for refactoring is a structured approach that maps dependency graphs to identify independent leaf nodes, allowing developers to implement incremental changes without breaking the existing codebase.

How does the Strangler Fig pattern work for code migration?▼

The Strangler Fig pattern works for code migration by gradually building a new system alongside the existing one, routing functionality incrementally until the old system can be safely retired.

What's the best way to track incremental refactoring progress?▼

Track incremental refactoring progress by maintaining dedicated tracking documents like a Mikado dependency graph and a Strangler migration plan, ensuring all tests pass before updating each stage.

Can I use Mikado and Strangler Fig together for legacy code refactoring?▼

Yes, you can use Mikado and Strangler Fig together for legacy code refactoring by leveraging Mikado to resolve deep dependency chains before applying Strangler Fig to incrementally migrate architecture components.

When should I avoid incremental refactoring techniques?▼

Avoid incremental refactoring techniques like Mikado and Strangler Fig for small, isolated code changes where the overhead of mapping dependencies and maintaining functional parity outweighs the coordination benefits.