gcp-to-aws

# GCP-to-AWS Migration Skill ## Philosophy - **Re-platform by default**: Select AWS services that match GCP workload types (e.g., Cloud Run → Fargate, Cloud SQL → RDS). - **Dev sizing unless specified**: Default to development-tier capacity (e.g., db.t4g.micro, single AZ). Upgrade only on user direction. - **Infrastructure-first approach**: v1.0 migrates Terraform-defined infrastructure only. App code scanning and billing import are v1.1+. ## Prerequisites User must provide GCP infrastructure-as-code: - One or more `.tf` files (Terraform) - Optional: `.tfvars` or `.tfstate` files If no Terraform files are found, stop immediately and ask user to provide them. ## State Management Migration state lives in `.migration/[MMDD-HHMM]/` directory (created by Phase 1, persists across invocations): ``` .migration/ ├── .gitignore # Auto-created to protect state files from git └── 0226-1430/ # MMDD-HHMM timestamp ├── .phase-status.json # Current phase tracking ├── gcp-resource-inventory.json # All GCP resources found ├── gcp-resource-clusters.json # Clustered resources by affinity ├── clarified.json # User answers (Phase 2 output) ��── aws-design.json # AWS services mapping (Phase 3 output) ├── estimation.json # Cost breakdown (Phase 4 output) └── execution.json # Timeline + risks (Phase 5 output) ``` **Note:** The `.migration/` directory is a...