schema-evolution-governance
Schema Evolution Governance
Overview
Use this skill to evolve shared schemas without breaking producers, consumers, or historical data integrity.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Compatibility window rules:
references/compatibility-window-rules.md
Templates And Assets
- Schema change plan template:
assets/schema-change-plan-template.md
- Schema compatibility checklist:
assets/schema-compatibility-checklist.md
Inputs To Gather
- Current schema and migration history.
- Producer/consumer dependency map.
- Data volume, retention, and rollback constraints.
- Release window and coordination limits.
Deliverables
- Compatibility-aware schema change plan.
- Phased migration sequence with checkpoints.
- Rollback and data-recovery readiness criteria.
Workflow
- Define change impact in
assets/schema-change-plan-template.md. - Apply compatibility rules from
references/compatibility-window-rules.md. - Validate consumer migration sequence and cutover plan.
- Verify rollback/data integrity with
assets/schema-compatibility-checklist.md. - Publish execution ownership and residual risk log.
Quality Standard
- Compatibility impact is explicit and testable.
- Migration and rollback paths are both validated.
- Consumer coordination is planned before destructive changes.
Failure Conditions
- Stop when forward/backward compatibility is unverified.
- Stop when rollback or data recovery path is missing.
- Escalate when migration risk exceeds governance policy.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9