schema-evolution-governance

Define phased schema migration plans with compatibility and rollback checks.

7|Updated Feb 14, 2026

Search Tags:#rollback #schema #compatibility #migration #governance #evolution #data-integrity

Ready to run

npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill schema-evolution-governance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: schema-evolution-governance
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/schema-evolution-governance
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill schema-evolution-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Schema evolution governance workflow for safe migration sequencing, compatibility control, and rollback readiness across dependent systems. Use when shared schemas change and end-to-end compatibility governance is required; do not use for isolated query micro-optimizations.

Core Features & Use Cases

Compatibility-aware change planning: define changes with phased migration and compatibility checks, ensuring producers and consumers stay in sync.
References and templates: reuse compatibility-window-rules and plan templates to govern migrations and capture validation criteria.
End-to-end governance across producers, consumers, and historical data, with clear rollback readiness and data integrity checks.

Quick Start

Define the change using the provided change plan template and references, then run the skill to generate a phased migration sequence with checkpoints and rollback readiness criteria.

Frequently Asked Questions about schema-evolution-governance

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

FAQPage Schema

How do I coordinate schema migrations across producers and consumers safely?▼

You can coordinate schema migrations safely by defining the schema change and applying compatibility rules to develop a phased migration plan across producers and consumers, ensuring data integrity and rollback readiness at each checkpoint.

What is schema evolution governance and when do I need it?▼

Schema evolution governance is a workflow for safe migration sequencing, compatibility control, and rollback readiness across dependent systems. You need it when shared schemas change and end-to-end compatibility governance is required across producers and consumers.

How do I plan a schema migration with rollback readiness?▼

Plan a schema migration with rollback readiness by using compatibility-window-rules and plan templates to generate a phased migration sequence, including checkpoints, validation criteria, and rollback readiness criteria across producers and consumers.

When should I not use a schema evolution governance workflow?▼

You should not use a schema evolution governance workflow for isolated query micro-optimizations. It is specifically designed for shared schema changes requiring end-to-end compatibility governance across dependent systems.

How do I document ownership and residual risk during a schema migration?▼

Document ownership and residual risk during a schema migration by publishing ownership and risk logs, which capture validation criteria and document responsibilities across producers, consumers, and historical data.

Can I reuse compatibility rules for phased schema migrations?▼

Yes, you can reuse compatibility-window-rules and plan templates to govern migrations. These references help define changes with phased migration and compatibility checks, ensuring producers and consumers stay in sync.