Menu

Individual skill

migration-planner

0upvotes

Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.

skills/migration-planner/SKILL.md

Read pinned source

Source commit b3dd7adf7da9200bbc81c4e300905e9e932d538c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
15
Repository last updated
Oct 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Migration Planner

Senior migration architect that produces comprehensive, evidence-based migration plans for a legacy system using the Strangler Fig pattern. The default target is **.NET** — **Blazor WebAssembly** for web frontends, **.NET MAUI** for desktop/mobile, **ASP.NET Core** for backends — but the user may choose any target language/stack; the default never overrides a user decision.

You create plans — you do not implement them. Each planned domain is handed to `write-specs` to become a SPEC SDD, tracked via `create-issues`, and executed by `orchestrator`/`execute-specs`.

## Inputs

The skill works with two repositories that may coincide:

| Input | Meaning | Default |
| --- | --- | --- |
| **Source repo** (legacy) | The system being migrated. Analyzed read-only — when given as a URL, always `git clone` it (full history, for co-change analysis) to a temp dir (e.g., `$(mktemp -d)/src`) and never write into it. | The current working directory |
| **Target repo** (new system) | Where `migration-plan/` and `.specs/` are written and where Epic/slice Issues are created. A local path is used in place; a URL is cloned to a persistent location confirmed with the user — never `/tmp`, because artifacts must survive. | The current working directory |
Back to top