plan-migration

Creates detailed migration plans with risk assessment and emergency-ride documentation.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/gjalla/gjalla-plugin --skill plan-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-migration
Source: https://github.com/gjalla/gjalla-plugin/tree/main/claude/skills/plan-migration
Command: npx skills add https://github.com/gjalla/gjalla-plugin --skill plan-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrations are high-risk changes that alter shared systems; this skill provides a structured approach to plan deployments with clear rollback strategies, testing, and observability to prevent outages.

Core Features & Use Cases

  • Migration plan templates covering scope, pre-migration checks, stepwise execution, rollback, and success criteria
  • Expand-Contract pattern guidance to keep old and new systems in sync during transitions
  • Progressive delivery strategies including canaries, staged rollouts, and automated rollback triggers
  • Documentation and attestation workflows to capture system state before, during, and after migrations

Quick Start

Draft a complete migration plan for the upcoming production change, including rollback steps and monitoring.

Frequently Asked Questions about plan-migration

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

FAQPage Schema
What is the best way to plan a database schema migration with rollback?▼

A safe database schema migration requires a structured plan analyzing blast radius, applying the Expand-Contract pattern to keep systems in sync, and defining explicit rollback scripts and success criteria to prevent outages.

How do I execute a canary rollout for a production service deployment?▼

To execute a canary rollout, you implement progressive delivery strategies that use staged rollouts and automated rollback triggers, monitoring system state and blast radius to safely deploy service updates.

How does the Expand-Contract pattern work during infrastructure updates?▼

The Expand-Contract pattern works by expanding the new system alongside the old, synchronizing data during the transition, and contracting the old system only after validation, preventing downtime during infrastructure updates.

Can I use automated rollback triggers for staged rollouts in production migrations?▼

Yes, you can configure automated rollback triggers as part of your progressive delivery strategy, allowing staged rollouts to automatically revert if monitoring detects failures during the production migration.

When do I need a documented migration plan with attestation workflows?▼

You need a documented migration plan with attestation workflows when executing high-risk changes to shared systems, ensuring you capture system state before, during, and after migrations to prevent outages.

What should be included in pre-migration checks for a production rollout?▼

Pre-migration checks should include analyzing the current system state and blast radius, defining success criteria, and preparing rollback scripts to ensure the production rollout maintains observability and safety.