Detailed migration execution guide — strangler fig, parallel run, big bang, rollback procedures, data migration. Use when the user asks to "plan migration", "design cutover", "build migration playbook", "define rollback strategy", or mentions strangler fig, parallel run, data migration, legacy modernization.
Migration playbook provides detailed execution guidance for system migrations, covering strategy selection, data migration, cutover choreography, and rollback procedures. The skill produces migration playbooks, cutover checklists, and rollback plans that minimize risk during system transitions.
The user provides a migration context as $ARGUMENTS. Parse $1 as the migration/project name.
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40%) | tecnica (full, default){ESTRATEGIA}: strangler-fig | parallel-run | big-bang | phased | auto (default)graph TD
subgraph Core["Migration Playbook"]
A[Migration Strategy] --> B[Data Migration]
A --> C[Cutover Plan]
A --> D[Rollback Design]
end
subgraph Inputs["Inputs"]
E[Migration Context] --> A
F[Source/Target Systems] --> B
G[Downtime Tolerance] --> A
end
subgraph Outputs["Outputs"]
A --> H[Playbook de Migracion]
C --> I[Checklist de Cutover]
D --> J[Plan de Rollback]
B --> K[Plan Migracion Datos]
end
subgraph Related["Related Skills"]
L[software-architecture] -.-> A
M[testing-strategy] -.-> C
N[disaster-recovery] -.-> D
end
delivery_migration-playbook_{proyecto}_{WIP}.mddelivery_migration-playbook_{proyecto}_{WIP}.docxdelivery_migration-playbook_{proyecto}_{WIP}.html{fase}_{entregable}_{cliente}_{WIP}.xlsx{fase}_migration-playbook_{cliente}_{WIP}.pptx| Dimension | Peso | Criterio |
|---|---|---|
| Trigger Accuracy | 10% | Activa ante "migration", "cutover", "strangler fig", "rollback" sin confundir con deployment pipeline o release management |
| Completeness | 25% | Cubre estrategia, datos, cutover, rollback, comunicacion y hypercare sin huecos |
| Clarity | 20% | Checklist de cutover es hora-por-hora con responsables y gates go/no-go |
| Robustness | 20% | Maneja zero-downtime, dependencias circulares, rollback imposible y equipos sin experiencia |
| Efficiency | 10% | 8 pasos donde contexto alimenta estrategia que alimenta planes detallados |
| Value Density | 15% | Checklist y playbook son directamente ejecutables el dia del cutover |
Umbral minimo: 7/10 en cada dimension para considerar el skill production-ready.
Autor: Javier Montaño · Comunidad MetodologIA | Version: 1.0.0