metodologia-migration-playbook

Plan migration strategies and generate executable playbooks for system transitions.

Updated Mar 31, 2026

Search Tags:#planning #rollback #playbook #migration #data-migration #strategies #cutover

Ready to run

npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-migration-playbook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: metodologia-migration-playbook
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/specialized/migration-playbook
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-migration-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migration planning and execution are error-prone without a structured framework. This skill provides strategies (strangler fig, parallel run, big bang) and deliverables (playbook, cutover checklist, rollback plan, data migration plan, stabilization plan) to standardize complex migrations.

Core Features & Use Cases

Strategy selection based on risk, downtime, and complexity
Deliverables: migration playbook, cutover checklist, data migration plan, rollback design, stabilization plan
Use cases: legacy modernization, cloud migration, data center consolidation

Quick Start

Provide the migration name and preferred format to generate a tailored migration playbook.

Frequently Asked Questions about metodologia-migration-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the best way to plan a migration strategy for legacy system modernization?▼

A cutover checklist is a structured deliverable that sequences migration transitions and manages risk. It standardizes complex system transitions by defining actionable steps alongside rollback plans and data migration procedures.

How do I generate a rollback plan for an enterprise data migration?▼

A phased migration strategy incrementally transitions system components, reducing risk compared to a big bang approach. It applies to enterprise migrations by sequencing data transfer and cutover events to maintain system stability.

Can I use a parallel run approach for cloud migration with zero downtime?▼

A parallel run approach supports cloud migration by running source and target systems simultaneously. This strategy minimizes downtime tolerance requirements and ensures data transfer accuracy before the final cutover.

When should I not use a big bang migration strategy?▼

You should not use a big bang migration strategy when downtime tolerance is low or system complexity is high. Select phased or parallel run approaches instead to manage risk and ensure data transfer stability.