Menu
Migration strategy for data/schemas/contracts: compatibility, phases, verification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Mandatory baseline rules for any agent. Must be loaded before any work
Frontend design system practices: tokens, typography, color, layout, and component consistency.
Frontend UI/UX practices: flows, interaction states, accessibility-first UX, forms, and perceived performance.
Clean code execution rules for coding agents with verifiable quality gates.
Debugging requirements protocol from reproducible issue to verified fix and regression protection.
Requirement quality rules for coding tasks with traceable MUST/SHOULD and verifiable acceptance criteria.
| name | planning-migration-strategy |
| description | Migration strategy for data/schemas/contracts: compatibility, phases, verification |
<common_patterns> expand/contract dual-read / dual-write backfill in background versioned API / events </common_patterns>
Identify migration objects and dependencies (tables, indexes, consumers) Select a migration pattern and justify it (why it fits the constraints) Split into phases: preparation -> compatibility -> transfer -> cutover -> cleanup Define integrity/correctness verification (checksums, counts, sampling) Explicitly describe compatibility during the migration window (which versions coexist)<output_format>
<quality_rules> Data integrity verification exists (not only "ran the migration") Compatibility during the migration window is described explicitly </quality_rules>
