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_service_migration_plan.txt

View on GitHub
================================================================================
MIGRATION PLAN: 21031930da18
================================================================================
Source System: Legacy User Service (Java Spring Boot 2.x)
Target System: New User Service (Node.js + TypeScript)
Migration Type: SERVICE
Complexity Level: CRITICAL
Estimated Duration: 500 hours (20.8 days)
Created: 2026-02-16T13:47:34.565896

MIGRATION PHASES
----------------------------------------
1. INTERCEPT (100h)
   Description: Execute intercept phase
   Risk Level: MEDIUM
   Tasks:
     • Complete intercept activities
   Success Criteria:
     ✓ Intercept phase completed successfully

2. IMPLEMENT (100h)
   Description: Execute implement phase
   Risk Level: MEDIUM
   Dependencies: intercept
   Tasks:
     • Complete implement activities
   Success Criteria:
     ✓ Implement phase completed successfully

3. REDIRECT (100h)
   Description: Execute redirect phase
   Risk Level: MEDIUM
   Dependencies: implement
   Tasks:
     • Complete redirect activities
   Success Criteria:
     ✓ Redirect phase completed successfully

4. VALIDATE (100h)
   Description: Execute validate phase
   Risk Level: MEDIUM
   Dependencies: redirect
   Tasks:
     • Complete validate activities
   Success Criteria:
     ✓ Validate phase completed successfully

5. RETIRE (100h)
   Description: Execute retire phase
   Risk Level: MEDIUM
   Dependencies: validate
   Tasks:
     • Complete retire activities
   Success Criteria:
     ✓ Retire phase completed successfully

RISK ASSESSMENT
----------------------------------------
HIGH SEVERITY RISKS:
  • Service compatibility issues
    Category: technical
    Probability: medium | Impact: high
    Mitigation: Implement comprehensive integration testing
    Owner: Development Team

  • Feature parity gaps
    Category: business
    Probability: high | Impact: high
    Mitigation: Document feature mapping and acceptance criteria
    Owner: Product 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

MEDIUM SEVERITY RISKS:
  • Performance degradation
    Category: technical
    Probability: medium | Impact: medium
    Mitigation: Conduct load testing and performance benchmarking
    Owner: DevOps Team

  • Monitoring gap during transition
    Category: operational
    Probability: medium | Impact: medium
    Mitigation: Set up dual monitoring and alerting systems
    Owner: SRE 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:
  RETIRE:
    - Revert retire changes
    - Restore pre-retire state
    - Validate retire rollback success
    Estimated Time: 1500 minutes

  VALIDATE:
    - Revert validate changes
    - Restore pre-validate state
    - Validate validate rollback success
    Estimated Time: 1500 minutes

  REDIRECT:
    - Revert redirect changes
    - Restore pre-redirect state
    - Validate redirect rollback success
    Estimated Time: 1500 minutes

  IMPLEMENT:
    - Revert implement changes
    - Restore pre-implement state
    - Validate implement rollback success
    Estimated Time: 1500 minutes

  INTERCEPT:
    - Revert intercept changes
    - Restore pre-intercept state
    - Validate intercept rollback success
    Estimated Time: 1500 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