/cloud-migration-planning
Plan and execute cloud migrations with assessment, database migration, application refactoring, and cutover strategies across AWS, Azure, and GCP.
$ npx -y skills add aj-geddes/useful-ai-prompts --skill cloud-migration-planning --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/cloud-migration-planning
Context preview
The summary Claude sees to decide when to auto-load this skill.
Plan and execute cloud migrations with assessment, database migration, application refactoring, and cutover strategies across AWS, Azure, and GCP.
SKILL.md
cloud-migration-planning.SKILL.mdname: cloud-migration-planning
description: >
Plan and execute cloud migrations with assessment, database migration,
application refactoring, and cutover strategies across AWS, Azure, and GCP.
Cloud Migration Planning
Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
Overview
Cloud migration planning involves assessing current infrastructure, designing migration strategies, executing migrations with minimal downtime, and validating outcomes. Support lift-and-shift, replatforming, and refactoring approaches for smooth cloud adoption.
When to Use
- Moving from on-premises to cloud
- Cloud platform consolidation
- Legacy system modernization
- Reducing data center costs
- Improving scalability and availability
- Meeting compliance requirements
- Disaster recovery enhancement
- Technology refresh initiatives
Quick Start
Minimal working example:
# Cloud migration assessment tool
from enum import Enum
from typing import Dict, List, Tuple
from dataclasses import dataclass
class MigrationStrategy(Enum):
LIFT_AND_SHIFT = "lift_and_shift" # Rehost
REPLATFORM = "replatform" # Rehost with optimizations
REFACTOR = "refactor" # Rebuild for cloud
REPURCHASE = "repurchase" # Switch to SaaS
RETIRE = "retire" # Decommission
class ApplicationComplexity(Enum):
LOW = 1
MEDIUM = 2
HIGH = 3
@dataclass
class ApplicationAssessment:
name: str
complexity: ApplicationComplexity
dependencies: List[str]
estimated_effort: int # days
business_criticality: int # 1-10
current_costs: float # annual
// ... (see reference guides for full implementation)Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents | |---|---| | [Migration Assessment and Planning](references/migration-assessment-and-planning.md) | Migration Assessment and Planning | | [Database Migration Strategies](references/database-migration-strategies.md) | Database Migration Strategies | | [Terraform Migration Infrastructure](references/terraform-migration-infrastructure.md) | Terraform Migration Infrastructure | | [Cutover Validation Checklist](references/cutover-validation-checklist.md) | Cutover Validation Checklist |
Best Practices
✅ DO
- Perform thorough discovery and assessment
- Run parallel systems during transition
- Test thoroughly before cutover
- Have rollback plan ready
- Monitor closely post-migration
- Document all changes
- Train operations team
- Maintain previous systems temporarily
❌ DON'T
- Rush migration without planning
- Migrate without testing
- Forget rollback procedures
- Ignore dependencies
- Skip stakeholder communication
- Migrate everything at once
- Forget to update documentation
Read more
name: cloud-migration-planning description: > Plan and execute cloud migrations with assessment, database migration, application refactoring, and cutover strategies across AWS, Azure, and GCP.
Cloud Migration Planning
Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
Overview
Cloud migration planning involves assessing current infrastructure, designing migration strategies, executing migrations with minimal downtime, and validating outcomes. Support lift-and-shift, replatforming, and refactoring approaches for smooth cloud adoption.
When to Use
- Moving from on-premises to cloud
- Cloud platform consolidation
- Legacy system modernization
- Reducing data center costs
- Improving scalability and availability
- Meeting compliance requirements
- Disaster recovery enhancement
- Technology refresh initiatives
Quick Start
Minimal working example:
# Cloud migration assessment tool
from enum import Enum
from typing import Dict, List, Tuple
from dataclasses import dataclass
class MigrationStrategy(Enum):
LIFT_AND_SHIFT = "lift_and_shift" # Rehost
REPLATFORM = "replatform" # Rehost with optimizations
REFACTOR = "refactor" # Rebuild for cloud
REPURCHASE = "repurchase" # Switch to SaaS
RETIRE = "retire" # Decommission
class ApplicationComplexity(Enum):
LOW = 1
MEDIUM = 2
HIGH = 3
@dataclass
class ApplicationAssessment:
name: str
complexity: ApplicationComplexity
dependencies: List[str]
estimated_effort: int # days
business_criticality: int # 1-10
current_costs: float # annual
// ... (see reference guides for full implementation)Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents | |---|---| | [Migration Assessment and Planning](references/migration-assessment-and-planning.md) | Migration Assessment and Planning | | [Database Migration Strategies](references/database-migration-strategies.md) | Database Migration Strategies | | [Terraform Migration Infrastructure](references/terraform-migration-infrastructure.md) | Terraform Migration Infrastructure | | [Cutover Validation Checklist](references/cutover-validation-checklist.md) | Cutover Validation Checklist |
Best Practices
✅ DO
- Perform thorough discovery and assessment
- Run parallel systems during transition
- Test thoroughly before cutover
- Have rollback plan ready
- Monitor closely post-migration
- Document all changes
- Train operations team
- Maintain previous systems temporarily
❌ DON'T
- Rush migration without planning
- Migrate without testing
- Forget rollback procedures
- Ignore dependencies
- Skip stakeholder communication
- Migrate everything at once
- Forget to update documentation
488 production-ready AI prompts, all following a standardized template with validated quality gates. Transform ChatGPT, Claude, and other AI assistants into expert consultants.
Repo: aj-geddes/useful-ai-prompts
Other skills on useful-ai-prompts.
- /ab-test-analysis
Design and analyze A/B tests, calculate statistical significance, and determine sample sizes for conversion optimization and experiment validation
Open skill - /access-control-rbac
Implement Role-Based Access Control (RBAC), permissions management, and authorization policies. Use when building secure access control systems with fine-grained permissions.
Open skill - /accessibility-compliance
Implement WCAG 2.1/2.2 accessibility standards, screen reader compatibility, keyboard navigation, and a11y testing. Use when building inclusive web applications, ensuring regulatory compliance, or improving user experience for people with disabilities.
Open skill - /accessibility-testing
Test web applications for WCAG compliance and ensure usability for users with disabilities. Use for accessibility test, a11y, axe, ARIA, keyboard navigation, screen reader compatibility, and WCAG validation.
Open skill - /agile-sprint-planning
Plan and execute effective sprints using Agile methodologies. Define sprint goals, estimate user stories, manage sprint backlog, and facilitate daily standups to maximize team productivity and deliver value incrementally.
Open skill - /alert-management
Implement comprehensive alert management with PagerDuty, escalation policies, and incident coordination. Use when setting up alerting systems, managing on-call schedules, or coordinating incident response.
Open skill

