model-migration-plan
Plan the migration of an LLM feature from one model to another without breaking production. Use when a model is being deprecated, a newer model looks better or cheaper, or when asked how to upgrade models safely, run shadow traffic, or set rollback criteria for a model change. Produces a phased migration plan with eval gates, shadow/canary stages, prompt-adaptation notes, and rollback triggers. For choosing which model in the first place use model-selection-advisor.
npx skills add mohitagw15856/pm-claude-skills --skill model-migration-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Model Migration Plan Skill A model swap changes every output of your feature at once. This skill plans the migration like the risky deploy it is: eval first, shadow second, canary third — with numbers, not vibes, deciding each promotion. ## What This Skill Produces - A **phased migration plan** (eval → shadow → canary → full) with promotion criteria per phase - **Prompt adaptation notes** — what typically shifts between models and what to re-tune - **Rollback triggers** and the mechanics of rolling back fast - A **cost/latency delta forecast** for the new model ## Required Inputs Ask for (if not already provided): - **Current and target model** (and why: deprecation, quality, cost, latency) - **The feature's traffic and blast radius** — requests/day, who sees the output, what a bad output costs - **Existing evals** — a regression suite (see `prompt-regression-suite`) or at minimum golden examples; if none exist, phase 0 is building one - **The deadline**, if the migration is forced by a deprecation date ## Migration Phases **Phase 0 — Baseline.** Freeze a regression suite against the *current* model. Without a baseline, "the new model is fine" is unfalsifiable. Record current cos
- What This Skill Produces
- Required Inputs
- Migration Phases
- Prompt Adaptation Notes
- Rollback
- Output Format
- Model Migration Plan: [feature] — [current model] → [target model]
- Quality Checks
- Anti-Patterns
What does the model-migration-plan skill do?
Plan the migration of an LLM feature from one model to another without breaking production. Use when a model is being deprecated, a newer model looks better or cheaper, or when asked how to upgrade models safely, run shadow traffic, or set rollback criteria for a model change. Produces a phased migration plan with eval gates, shadow/canary stages, prompt-adaptation notes, and rollback triggers. For choosing which model in the first place use model-selection-advisor.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill model-migration-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.