Skip to content

borghei/Claude-Skills / engineering/migration-architect

migration-architect

Verified

Plans zero-downtime migrations with compatibility validation, rollback strategies, and phased execution plans. Use when migrating databases, APIs, infrastructure, or services between platforms or versions.

expected_outputs/sample_database_migration_plan.txt

View on GitHub
================================================================================
MIGRATION PLAN: 23a52ed1507f
================================================================================
Source System: PostgreSQL 13 Production Database
Target System: PostgreSQL 15 Cloud Database
Migration Type: DATABASE
Complexity Level: CRITICAL
Estimated Duration: 95 hours (4.0 days)
Created: 2026-02-16T13:47:23.704502

MIGRATION PHASES
----------------------------------------
1. PREPARATION (19h)
   Description: Prepare systems and teams for migration
   Risk Level: MEDIUM
   Tasks:
     • Backup source system
     • Set up monitoring and alerting
     • Prepare rollback procedures
     • Communicate migration timeline
     • Validate prerequisites
   Success Criteria:
     ✓ All backups completed successfully
     ✓ Monitoring systems operational
     ✓ Team members briefed and ready
     ✓ Rollback procedures tested

2. EXPAND (19h)
   Description: Execute expand phase
   Risk Level: MEDIUM
   Dependencies: preparation
   Tasks:
     • Complete expand activities
   Success Criteria:
     ✓ Expand phase completed successfully

3. MIGRATE (19h)
   Description: Execute migrate phase
   Risk Level: MEDIUM
   Dependencies: expand
   Tasks:
     • Complete migrate activities
   Success Criteria:
     ✓ Migrate phase completed successfully

4. CONTRACT (19h)
   Description: Execute contract phase
   Risk Level: MEDIUM
   Dependencies: migrate
   Tasks:
     • Complete contract activities
   Success Criteria:
     ✓ Contract phase completed successfully

5. CLEANUP (19h)
   Description: Execute cleanup phase
   Risk Level: MEDIUM
   Dependencies: contract
   Tasks:
     • Complete cleanup activities
   Success Criteria:
     ✓ Cleanup phase completed successfully

RISK ASSESSMENT
----------------------------------------
CRITICAL SEVERITY RISKS:
  • Insufficient rollback testing
    Category: operational
    Probability: high | Impact: critical
    Mitigation: Execute full rollback procedures in staging environment
    Owner: QA Team

HIGH SEVERITY RISKS:
  • Data corruption during migration
    Category: technical
    Probability: low | Impact: critical
    Mitigation: Implement comprehensive backup and validation procedures
    Owner: DBA Team

  • Extended downtime due to migration complexity
    Category: technical
    Probability: medium | Impact: high
    Mitigation: Use blue-green deployment and phased migration approach
    Owner: DevOps Team

  • Business process disruption
    Category: business
    Probability: medium | Impact: high
    Mitigation: Communicate timeline and provide alternate workflows
    Owner: Business Owner

  • Zero-downtime requirement increases complexity
    Category: business
    Probability: high | Impact: medium
    Mitigation: Implement blue-green deployment or rolling update strategy
    Owner: DevOps Team

  • Regulatory compliance requirements
    Category: compliance
    Probability: medium | Impact: high
    Mitigation: Ensure all compliance checks are integrated into migration process
    Owner: Compliance Team

ROLLBACK STRATEGY
----------------------------------------
Rollback Triggers:
  • Critical system failure
  • Data corruption detected
  • Migration timeline exceeded by > 50%
  • Business-critical functionality unavailable
  • Security breach detected
  • Stakeholder decision to abort

Rollback Phases:
  CLEANUP:
    - Revert cleanup changes
    - Restore pre-cleanup state
    - Validate cleanup rollback success
    Estimated Time: 285 minutes

  CONTRACT:
    - Revert contract changes
    - Restore pre-contract state
    - Validate contract rollback success
    Estimated Time: 285 minutes

  MIGRATE:
    - Revert migrate changes
    - Restore pre-migrate state
    - Validate migrate rollback success
    Estimated Time: 285 minutes

  EXPAND:
    - Revert expand changes
    - Restore pre-expand state
    - Validate expand rollback success
    Estimated Time: 285 minutes

  PREPARATION:
    - Revert preparation changes
    - Restore pre-preparation state
    - Validate preparation rollback success
    Estimated Time: 285 minutes

SUCCESS CRITERIA
----------------------------------------
✓ All data successfully migrated with 100% integrity
✓ System performance meets or exceeds baseline
✓ All business processes functioning normally
✓ No critical security vulnerabilities introduced
✓ Stakeholder acceptance criteria met
✓ Documentation and runbooks updated

STAKEHOLDERS
----------------------------------------
• Business Owner
• Technical Lead
• DevOps Team
• QA Team
• Security Team
• End Users
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall