From codex-next
Plans safe migrations for technology, framework, architecture, schema, or large-scale rewrites with phased rollback and validation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codex-next:dev-migration-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this workflow when changing technology, framework, architecture, schema, or large old-system behavior must be planned safely.
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/_资产.mdlocal/sdlc/架构.md for as-built and to-be architecture.local/sdlc/领域.md for ownership, data, allowed dependencies, and forbidden dependencies.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.
Define target and non-goals.
Map current behavior.
as-built notes from 架构.md or repository evidenceChoose migration strategy.
Build safety rails.
领域.mdBreak into phases.
Update durable ADS only when needed.
local/sdlc/架构.mdlocal/sdlc/领域.mdlocal/sdlc/_资产.mdlocal/sdlc/<slug>/00-状态.mdReturn:
npx claudepluginhub blueskyxn/codex-is-all-you-need --plugin codex-nextPlan large-scale migrations from old systems to new architectures. Use when modernizing legacy systems or upgrading infrastructure.
Orchestrates complete migration workflows for frameworks (e.g., Vue 2→3, Express→Fastify), databases (MySQL→PostgreSQL), and architectures (REST→GraphQL, monolith→microservices) with analysis, incremental execution, and rollback.
Orchestrates full migration workflows from current state analysis through planning, incremental implementation, and verification for technologies, platforms, and architecture patterns with rollback planning.