Individual skill
migration-planner
Plans a safe, incremental migration (framework, database, service, or platform) with rollback points and a dual-running strategy. Use when replacing something that's already in production and can't just be swapped in one step.
skills/architecture/migration-planner/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- 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)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,395 bytesSKILL.mdcore · 2,848 bytesexamples/example.mddoc · 2,625 bytes
Read excerpt
## Purpose
Plan a migration from an existing system to a new one in incremental, individually-reversible steps — so the migration can be paused, verified, or rolled back at any point, rather than being a single high-risk cutover.
## When to Use
- Migrating a framework, database, service, or platform that's already running in production.
- Replacing a component where a big-bang cutover would be too risky to attempt.
- The user asks how to "migrate," "move off," or "replace" something existing.
Differs from [Project Planner](../project-planner/): that plans building something new; this plans *replacing* something that already exists and must keep working throughout.
## What to Analyze / Do