platform-migration-plan

Name: platform-migration-plan
Availability: InStock
Author: oalansilva

Plan phased platform migrations with stages, validation criteria, and rollback paths.

Updated Dec 28, 2025

Search Tags:#planning #rollback #dependencies #migration #platform #downtime

Ready to run

npx skills add https://github.com/oalansilva/crypto --skill platform-migration-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: platform-migration-plan
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/infra/platform-migration-plan
Command: npx skills add https://github.com/oalansilva/crypto --skill platform-migration-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a plan to migrate platforms or runtimes, mitigating risk and aligning stakeholders with a clear, staged approach.

Core Features & Use Cases

Migration assessment: identify dependencies and constraints for both source and target environments.
Stage-wise planning: define migration phases, compatibility layers, and validation steps.
Rollback readiness: document rollback paths and success criteria for each stage.
Use Case: when migrating a legacy platform to a newer runtime, generate a timeline with milestones and verification steps.

Quick Start

Provide a current platform and target platform to generate a phased migration plan.

Frequently Asked Questions about platform-migration-plan

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

FAQPage Schema

How do I plan a platform migration with minimal downtime?▼

A platform migration plan structures the transition into stages with defined validation criteria and rollback paths to minimize downtime. It assesses dependencies and compatibility constraints for both source and target environments to ensure a staged, low-risk transition.

What is the best way to map dependencies before migrating runtimes?▼

Mapping dependencies during a platform migration involves assessing both source and target environments to identify constraints and required compatibility layers. The plan evaluates these dependencies to structure migration phases accurately and mitigate risk.

How do I create a rollback plan for a staged platform migration?▼

Create a rollback plan by documenting specific rollback paths and defining success metrics for each stage of the platform migration. This rollback readiness ensures you can safely revert if validation criteria fail during a specific migration phase.

Can I use a phased migration plan for a legacy platform upgrade?▼

Yes, a phased migration plan supports migrating a legacy platform to a newer runtime by generating a timeline with milestones and verification steps. It defines specific migration stages and compatibility layers to ensure the legacy system transitions safely.

What do I need to provide to generate a platform migration roadmap?▼

To generate a platform migration roadmap, you need to provide the current platform and the target platform. The plan then applies your project's dependencies, downtime tolerance, and rollback needs to produce a structured, staged roadmap.

What are the limitations of using a staged platform migration approach?▼

A staged platform migration requires clearly defined downtime tolerance and compatibility layers, meaning it may not suit projects where zero downtime is mandated without parallel run capabilities. The plan relies on accurate dependency mapping to establish valid rollback paths.