migration-strategies

migration-strategies is a skill for Claude Code from Vimalk0703/shipworthy. It costs 42 tokens per session (2,450 once invoked), scanned A, original, MIT.

A guide for moving from an old system to a new one in controlled stages. It covers approaches such as replacing parts gradually, running old and new systems together, changing schemas in steps, switching between environments, and using feature flags.

In plain words
What is it for?
Use it when replacing a monolith, data-processing system, database schema, API, application deployment, or internal algorithm.
Why use it?
It helps reduce the risk of a large system change by keeping rollback and verification in the plan. A rollback returns the system to the previous version if the new one fails.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the shipworthy plugin — 66 skills, 7 commands, 3 hooks shipped together

Good fit Use it when replacing a monolith, data-processing system, database schema, API, application deployment, or internal algorithm.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vimalk0703/shipworthy/migration-strategies
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Vimalk0703/shipworthy --skill migration-strategies
Clone the repo
git clone --depth 1 https://github.com/Vimalk0703/shipworthy

Made for: Claude Code.

Or install shipworthy, the plugin that ships this one along with the rest of its 66 skills, 7 commands, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for migration-strategies

README.md
[![agentmods](https://agentmods.dev/badge/skills/vimalk0703/shipworthy/migration-strategies/github.svg)](https://agentmods.dev/skills/vimalk0703/shipworthy/migration-strategies)
Your own site
<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/migration-strategies"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/migration-strategies/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for migration-strategies

Your own site · 80×15
<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/migration-strategies"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/migration-strategies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.02450
Opus 5 $0.00021 $0.01225
Sonnet 5 $0.00008 $0.00490
Haiku 4.5 $0.00004 $0.00245

Measured 10d ago against content hash f7419a598cf5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

migration-strategies scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/operations/migration-strategies/SKILL.md · 289 lines

How it starts

The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migration Strategies

Core Principle

Every migration must be reversible until fully verified. Never cut over to a new system without running it alongside the old one first. The migration strategy you choose determines your risk profile, rollback speed, and verification confidence.


Decision Matrix

Strategy Best For Rollback Speed Complexity Data Migration?
Strangler Fig Replacing a monolith with microservices Fast (route traffic back) Medium Gradual
Parallel Run Replacing a critical data processing system Instant (read from old) High Yes, bidirectional
Expand-Contract Database schema changes, API changes Medium (revert schema) Low-Medium In-place
Blue-Green Full application deployments Instant (swap environments) Medium Shared or replicated
Feature Flag Migration Replacing internal components or algorithms Instant (toggle flag) Low Depends

1. Strangler Fig Pattern

When to Use

  • Migrating from a monolith to microservices.
  • Replacing a legacy system piece by piece over weeks or months.
  • You want to avoid a big-bang rewrite.

How It Works

  1. Place a routing layer (API gateway, reverse proxy) in front of the legacy system.
  2. Build new functionality in the new system.
  3. Route traffic for specific endpoints/features to the new system.
  4. Gradually expand the new system's surface area until the legacy system handles nothing.
  5. Decommission the legacy system.
Phase 1:  Client -> Gateway -> Legacy System (all traffic)
Phase 2:  Client -> Gateway -> Legacy System (most traffic)
                            -> New Service A (/users)
Phase 3:  Client -> Gateway -> Legacy System (some traffic)
                            -> New Service A (/users)
                            -> New Service B (/orders)
Phase N:  Client -> Gateway -> New Services (all traffic)
                               Legacy System (decommissioned)

Implementation

Read the full file on GitHub · 289 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 289 lines · 42 tokens per session scan A f7419a598cf5

Subscribe to this mod's changes

migration-strategies is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 2,450 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

hedgehog-planning-intake

Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…

skyf0xx/hedgehog · 0 tokens

bmad-product-brief

Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

skyf0xx/hedgehog · 31 tokens

bmad-deep-recon

Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here…

skyf0xx/hedgehog · 167 tokens

hedgehog

Use when the user writes the word "Hedgehog" anywhere in a request, or has agreed to install the Hedgehog build discipline in a project that does not have it yet. Hedgehog builds prose as well as code — articles, essays, blog posts, tweets, threads, newsletters, announcements, and marketing or product copy of any…

skyf0xx/hedgehog · 0 tokens

conventional-commits

Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…

skyf0xx/hedgehog · 88 tokens

hedgehog-contributing

Use when the user wants to contribute a fix or roadmap item back to the Hedgehog project itself (skyf0xx/hedgehog) rather than their own project. Triggers on "let's fix that in Hedgehog", "I want to contribute", "let's pick up a roadmap item", or when tweaker offers this at the end of a build and the user says yes.…

skyf0xx/hedgehog · 118 tokens