schema-evolution-planner

What problem does it solve?

This Skill helps you plan schema changes on live systems without breaking deployed readers and writers, especially when rolling deploys, overlapping code versions, and multi-release cutovers make a one-step rename or retype unsafe.

Core Features & Use Cases

• Expand → Migrate → Contract Planning: Designs additive-first rollout stages for renames, splits, merges, retypes, and constraint tightening.
• Consumer Enumeration: Identifies affected application models, raw queries, background jobs, event serializers, and analytics extracts that must remain compatible during the rollout.
• Verification Gates and Deprecation Control: Defines parity checks, zero-reader evidence, release mapping, rollback boundaries, and deprecation-register entries before any physical drop.
• Use Case: Use this Skill when splitting a live column into two fields, retiring a legacy column across several releases, or coordinating a schema evolution with rolling production deploys.

Quick Start

Ask the schema-evolution-planner to stage the live rename or retype, list all readers and writers, and produce an expand-migrate-contract plan with verification gates and release boundaries.