expand-contract-migration

Name: expand-contract-migration
Availability: InStock
Author: buchananwill

Coordinates zero-downtime expand-migrate-contract database migrations for production systems.

2|Updated Mar 17, 2026

Search Tags:#migration #zero-downtime #release-management #schema-evolution #data-migration #production-database #expand-contract

Ready to run

npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill expand-contract-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: expand-contract-migration
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/expand-contract-migration
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill expand-contract-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zero-downtime database migrations in production by coordinating additive changes, concurrent reads, and final deprecation of old structures.

Core Features & Use Cases

End-to-end migration protocol (Expand, Migrate, Contract) for live systems
Separation of schema and data migrations with strict forward-only rules
Production-ready guardrails, auditing timeline, and rollback strategies

Quick Start

Follow the three-phase expand-contract protocol to safely deploy a production database migration.

Frequently Asked Questions about expand-contract-migration

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

FAQPage Schema

What is the expand-contract pattern for zero-downtime database migrations?▼

The expand-contract pattern is a zero-downtime schema evolution protocol coordinating additive changes, concurrent reads, and final deprecation of old structures. It separates schema and data migrations to let live systems run without interruption during deployment.

How do I perform a production database schema evolution without downtime?▼

To perform production database schema evolution without downtime, follow the expand-migrate-contract protocol. This enforces strict forward-only rules, separates schema and data migrations, and applies production guardrails during column or table restructures.

When do I need to use forward-only rules for schema evolution?▼

You need forward-only rules for schema evolution when coordinating zero-downtime migrations where old and new database shapes must coexist. This discipline guarantees safe additive changes and final deprecation without breaking concurrent production reads.

Can I separate schema and data migrations during a live production deployment?▼

Yes, you can and should separate schema and data migrations during live production deployments. The expand-contract protocol enforces this separation to coordinate additive changes and concurrent reads while maintaining strict forward-only guarantees.

What are the limitations of the expand-contract migration protocol?▼

The expand-contract migration protocol requires strict forward-only guarantees and separation of schema and data migrations. It demands robust production guardrails and careful auditing timelines, making it unsuitable for rapid, uncoordinated database restructures.