Agent skill · magnus919
migration-engineering
Plan and execute safe cross-system migrations, including service extraction from monoliths. Use when moving data, schemas, interfaces, infrastructure, or service ownership through compatibility windows, dual-running, reconciliation, cutover, recovery, or deprecation. Do not use for deciding whether decomposition is justified, designing a target architecture, or implementing one named technology; route those to the relevant architecture or specialist skill.
What it needs
About 11k tokens when loaded.
What this skill does
Migration Engineering Plan and execute safe migrations across system boundaries. A migration is any change that moves data, schemas, interfaces, infrastructure, or services from a current state to a target state while preserving correctness, availability, and recoverability during the transition. This skill owns the cross-system migration method — compatibility design, staging, reconciliation, cutover, recovery, and deprecation. It does not own the implementation details of any single technology or subsystem; those belong to specialist skills. When to use Load this skill when the task involves: Trigger Example --- --- A schema change that must not break existing readers or writers "Add a non-nullable column to a high-traffic table with zero downtime" A data migration between stores or representations "Migrate user profiles from Postgres to a dedicated service with its own database" An API version migration with a deprecation window "Move consumers from v1 REST to v2 GraphQL over six months" An infrastructure or service migration "Shift a workload from self-hosted VMs to a managed platform across regions" A cross-system change requiring dual-running and reconciliation "Replace the legacy billing engine with a new one while keeping both in sync" Planning cutover, rollback, or irreversible steps for a migration "Define the recovery strategy for the warehouse schema migration" When not to use Single-technology quick fixes — if the change is confined to one system with no compatibility window, no dual-running, and no cross-system coordination, use the relevant specialist skill directly (e.g., data-engineering for a simple DDL change, api-design-and-evolution for a single-endpoint deprecation). Tool-specific how-to guides — this skill provides the method, not vendor-specific instructions. It does not prescribe one migration technology, one database engine, one API gateway, or one infrastructure platform. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/migration-engineering