Skip to content
Skills Library
Programming · Planning

dev-migration-plan

/dev-migration-plan

Use to plan modernization, framework upgrades, service extraction, schema migrations, rewrites, and rollback paths.

Licence
GPL-3.0
Last repository change
17.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.09.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Use to plan modernization, framework upgrades, service extraction, schema migrations, rewrites, and rollback paths.

Original author description

Use to plan modernization, framework upgrades, service extraction, schema migrations, rewrites, and rollback paths.

How it works

  1. Steps
  2. Output
  3. Do not
Original SKILL.md headings · 82 lines, 380 words
SKILL.md preview
---
name: dev-migration-plan
description: Use to plan modernization, framework upgrades, service extraction, schema migrations, rewrites, and rollback paths.
metadata:
  version: "0.6"
  updated: "2026-07-26"
---

# Migration plan workflow

Use this workflow when changing technology, framework, architecture, schema, or large old-system behavior must be planned safely.

When present, consume the SDLC-ADS state before planning:

- `local/sdlc/_资产.md`
- `local/sdlc/架构.md` for `as-built` and `to-be` architecture.
- `local/sdlc/领域.md` for ownership, data, allowed dependencies, and forbidden dependencies.
- current `local/sdlc/<slug>/00-状态.md` for lane, stage, decisions, blockers, and validation state.

For pure refactor or migration, prefer behavior baseline, `as-built`, `to-be`, phases, validation, and rollback. Do not require Product Pack material unless the migration changes user behavior, business semantics, permissions, data ownership, or release commitments.

## Steps

1. Define target and non-goals.
   - What is being migrated
   - What must remain compatible
   - What can change
   - Constraints and deadlines

2. Map current behavior.
   - Entry points
   - Core business flows
   - Data model
   - External integrations
   - Tests and monitoring
   - Known risk areas
   - Existing `as-built` notes from `架构.md` or repository evidence

3. Choose migration strategy.
   - Incremental replacement
   - Adapter/facade
   - Strangler pattern
   - Parallel run
   - Feature flag rollout
   - Backward-compatible schema transition
   - Architecture/domain constraint preservation
   - If the trade-off set is still contested, recommend
     `$codex-next:core-grilling` and stop. Wait for the user to invoke it
     explicitly; do not imitate or begin that workflow here.

4. Build safety rails.
   - Characterization tests
   - Contract tests
   - Data backup or rollback
   - Observability
   - Stop conditions
   - Behavior baseline for externally visible behavior
   - Dependency and ownership checks from `领域.md`

5. Break into phases.
   - Small milestones
   - Validation after each phase
   - Rollback path
   - Owner and dependency assumptions

6. Update durable ADS only when needed.
   - New durable architecture constraints -> `local/sdlc/架构.md`
   - New ownership or dependency constraints -> `local/sdlc/领域.md`
   - New decisions or validation baseline -> `local/sdlc/_资产.md`
   - Current delivery state -> `local/sdlc/<slug>/00-状态.md`

## Output

Return:

1. Current-state map
2. Target state
3. Phased migration plan
4. Validation and rollback strategy
5. ADS impact and durable state updates needed
6. Risks and open decisions

## Do not

- Do not propose a big-bang rewrite unless explicitly requested.
- Do not ignore current behavior just because the old code is messy.
- Do not start implementation before the safety path is clear.
- Do not treat refactor/migration as a PRD problem unless product or domain semantics change.

Versions

The database has no other skills named dev-migration-plan.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 299b20437928 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 84migration-assistant
    [UDS] 引导系统性的代码迁移、框架升级与技术现代化。 Use when: 规划框架或主版本升级、评估迁移风险、在 API 迁移前先抓取契约测试的固定样本。 Not for: 维持同一套框架的原地改善——请用 /refactor;数据库 schema 设计——请用 /database。 Keywords: migration, framework upgrade, modernization, breaking change, dependency upgrade, 迁移, 升级, 技术现代化, 破坏性变更.
  • 90safe-migration
    Plan and execute a controlled migration of code, schemas, frameworks, or configuration while preserving a rollback path. Use when changing formats, APIs, databases, runtimes, or major dependencies.
  • 90dev-writing-migrations
    Use when a change touches a live Postgres/MySQL schema: migration-plan.md at G3, migration files at G7, expand → migrate → contract, real rollback.
  • 95prisma-next-migrations
    Author Prisma Next migrations — choose db update vs migration plan, edit the framework-rendered migration.ts (replace placeholder sentinels with dataTransform closures), recover from MIGRATION.HASH_MISMATCH or PN-MIG-2001 unfilled placeholder. Use for prisma migrate dev, prisma…
  • 100agent-migration-specialist
    Specialist subagent: Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration,…
  • 100dependency-analyzer
    Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.