Skip to content
Back to skills

Strangler Fig Migration

ASecurity

Plan an incremental strangler-fig migration off a legacy system — a facade routing one capability at a time to a new implementation behind an anti-corruption layer. Reach for this instead of a big-bang rewrite.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agents

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill strangler-fig-migration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Strangler Fig Migration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Strangler Fig Migration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-strangler-fig-migration/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-strangler-fig-migration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: strangler-fig-migration
description: "Plan an incremental strangler-fig migration off a legacy system — a facade routing one capability at a time to a new implementation behind an anti-corruption layer. Reach for this instead of a big-bang rewrite."
---

# Skill: Strangler-fig migration

Replace the old system one capability at a time, value landing continuously, rollback always a route-flip away (§2 #4).

## Step 1 — Place the facade
Put an interception point (gateway / facade / abstraction) in front of the legacy system so requests can be routed to old *or* new per capability.

## Step 2 — Pick the first capability
Choose a slice that is high-value or high-risk-to-learn and has a clean seam (from `codebase-archaeologist`). Small enough to ship; meaningful enough to prove the pattern.

## Step 3 — Build behind an anti-corruption layer
Implement the new version with an ACL translating between the legacy model and the new model (§2 #5), so the old quirks don't leak into the new design.

## Step 4 — Route incrementally
Shift traffic for that capability gradually (canary / cohort), watching SLOs and reconciliation. Keep the old path live as the rollback.

## Step 5 — Repeat, then remove the facade
Migrate capabilities one by one until the legacy system is dead, then retire the facade. Branch-by-abstraction is the in-process variant of the same idea.

> Decision support: the cutover-strategy tree in [`../../knowledge/legacy-modernization-decision-trees.md`](../../knowledge/legacy-modernization-decision-trees.md) and the pattern catalog in [`../../knowledge/modernization-patterns-reference.md`](../../knowledge/modernization-patterns-reference.md).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…