Cloud Migration: Assessment, Planning & Execution

Generic, brand-neutral engineering capability; deep, sourced playbooks live in references/ and knowledge/. [DOC]

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Cloud migration moves workloads from on-premises or legacy environments to cloud platforms. This skill produces comprehensive migration plans covering 7R assessment, workload analysis, wave planning, landing zone design, execution patterns, and post-migration optimization [EXPLICIT]

When to Use

• Planning migration of workloads from on-premises to cloud
• Classifying applications using the 7R framework
• Mapping application dependencies for migration sequencing
• Designing cloud landing zones for migrated workloads
• Planning migration waves and cutover execution
• Validating post-migration performance and decommissioning legacy systems

When NOT to Use

• Designing cloud-native architecture for new applications --> use cloud-native-architecture skill
• Infrastructure platform design (VPC, compute, storage) --> use infrastructure-architecture skill
• Current-state analysis without migration intent --> use asis-analysis skill
• Enterprise portfolio strategy --> use enterprise-architecture skill

---

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: · Does not design cloud-native architecture for refactored applications (use cloud-native-architecture skill) · Does not design infrastructure platform from scratch (use infrastruc. [EXPLICIT]
• Casos borde: Datacenter Exit with Hard Deadline: Favor rehost for speed. Accept technical debt. Plan post-migration optimization waves. Prioritize by lease expiry. [EXPLICIT]
• Supuestos: · Target cloud platform selected (AWS, Azure, GCP, or multi-cloud) · Application inventory exists or can be discovered · Budget approved for migration (dual-run costs included) · T. [SUPUESTO]
• Trade-off: Decision Enables Constrains When to Use --- --- --- --- Rehost Speed, low risk No modernization Datacenter exit deadline Replatform Some cloud benefit, mo. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.