migration-plan

migration-plan is a command for GitHub Copilot from yuri-semenenko/ai-engineering-workspace. It costs 20 tokens per session (473 once invoked), scanned A, original, MIT.

A planning prompt for breaking a risky migration or refactor into small, reversible steps while keeping user-visible behavior unchanged.

In plain words
What is it for?
Use it to plan characterization tests, incremental releases, feature-flagged transitions, and rollback paths for migrations.
Why use it?
It reduces the chance that a framework upgrade, API move, or legacy replacement becomes an unsafe big-bang change.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

Good fit Use it to plan characterization tests, incremental releases, feature-flagged transitions, and rollback paths for migrations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yuri-semenenko/ai-engineering-workspace/migration-plan
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.

Clone the repo
git clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspace

Made for: GitHub Copilot.

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-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/yuri-semenenko/ai-engineering-workspace/migration-plan/github.svg)](https://agentmods.dev/commands/yuri-semenenko/ai-engineering-workspace/migration-plan)
Your own site
<a href="https://agentmods.dev/commands/yuri-semenenko/ai-engineering-workspace/migration-plan"><img src="https://agentmods.dev/badge/commands/yuri-semenenko/ai-engineering-workspace/migration-plan/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-plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/yuri-semenenko/ai-engineering-workspace/migration-plan"><img src="https://agentmods.dev/badge/commands/yuri-semenenko/ai-engineering-workspace/migration-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 473 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.00020 $0.00473
Opus 5.5 $0.00008 $0.00189
Sonnet 5.5 $0.00004 $0.00095
Haiku 4.5 $0.00002 $0.00047

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

Security

Grade A, and why

migration-plan 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 5d 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.

copilot/workspace-template/.github/prompts/migration-plan.prompt.md · 37 lines

What it actually says

Migration Plan Prompt

Role: Act as a senior engineer planning a risky migration or refactor — a framework upgrade, design-system swap, API version migration, or legacy-to-modern replacement.

Context: The decision to migrate has been made (an RFC or equivalent). What is needed now is the executable plan: how to get there safely and reversibly without changing user-visible behavior.

Task: Produce a migration plan that sequences the work into small, independently shippable, reversible slices.

Constraints:

  • Behavior-preserving by default. Keep new behavior or features as a separate change, after the migration.
  • Every slice must be independently shippable and reversible; no step that can only be undone by a second migration. A step that writes data or external state says what a rerun after a partial failure does: idempotent, skips finished work, or a named recovery procedure. Do not assume idempotency, and do not count a retry as a rollback.
  • Capture the invariant (user-visible behavior that must not change) as characterization tests or golden output before touching anything.
  • Feature flags are temporary: name the removal trigger and date when you add one.
  • Prefer incremental over big-bang; if a big-bang cutover is unavoidable, say why and how you rehearse it.
  • Delegate the read-only inventory and characterization (call sites, seam, current behavior) to a focused gathering pass; keep the invariant, migration shape, and rollback criteria as the main judgment.

Output Format:

  1. The invariant, and how it is captured (characterization tests / golden output)
  2. Current to target, and the seam you migrate across
  3. Migration shape and why: strangler / adapter / expand-contract / branch-by-abstraction
  4. Ordered slices, each with its before/after verification, flag, rollback criteria, and rerun behavior where it writes state
  5. Rollout and rollback plan, ending with flag and dead-code cleanup
  6. The highest-risk or least-reversible step, and its mitigation

Success Criteria:

  • The system is releasable and reversible after every slice.
  • User-visible behavior is provably unchanged at each step.
  • Every feature flag has a named removal trigger.
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. 5d ago Changed 148b61259dbb
  2. 6d ago First seen · 37 lines · 20 tokens per session scan A 12c2239feb7a

Subscribe to this mod's changes

migration-plan is a command published in the GitHub repository yuri-semenenko/ai-engineering-workspace (4 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 473 once invoked, about $0.0001 per session on Opus 5.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-10-31.

Related

migration-plan compared with commands from other repositories

migration-plan next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
migration-planyuri-semenenko/ai-engineering-workspaceCommand43d agoMITA20GitHub Copilot
spec-trace-requirementsrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
ios-buildNagarjuna2997/ios-agent-skillCommand408d agoMITA19Claude Code
sdd-setupGregorBiswanger/featherspecCommand701mo agoMITA27Claude Code
playwright-executekatalon-labs/true-skillsCommand1017d agoMITA117GitHub Copilot
test-maintenancekatalon-labs/true-skillsCommand1017d agoMITA131GitHub Copilot