db-migration-strategy
DB Migration Strategy
Overview
Use this skill to evolve schemas in production without service disruption or hidden data corruption.
Scope Boundaries
- Schema changes affect live read/write paths.
- Multiple service versions must coexist during rollout.
- Data backfill or contract transition is required.
Core Judgments
- Migration pattern: expand-contract, dual-write, shadow-read, or phased cutover.
- Compatibility window duration and supported versions.
- Backfill approach and execution safety.
- Rollback semantics and data reconciliation strategy.
Practitioner Heuristics
- Prefer additive/compatible changes before destructive cleanup.
- Separate schema deployment from application behavior switch.
- Dual-write without reconciliation plan is a corruption risk.
- Large backfills need throttling and progress observability tied to business impact.
Workflow
- Define change classes: additive, transitional, destructive.
- Sequence schema and application releases for compatibility.
- Plan data migration/backfill and failure handling.
- Define cutover trigger and rollback decision points.
- Execute deprecation/removal only after compatibility window closes.
- Document residual migration debt and retirement deadlines.
Common Failure Modes
- Breaking changes shipped before all consumers are updated.
- Backfill jobs compete with production traffic and cause incidents.
- Rollback plan restores code but not data semantics.
Failure Conditions
- Stop when compatibility window cannot be supported operationally.
- Stop when rollback semantics for migrated data are undefined.
- Escalate when migration risk exceeds release risk tolerance.
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