Summary

This skill provides a framework for planning and executing safe, reversible migrations across schema, data, API, protocol, configuration, or dependency systems. It emphasizes preserving existing data, enabling rollback, supporting mixed-version operation, and making destructive steps explicit. The skill teaches strategic sequencing (expand → migrate → verify → contract) and observability rather than providing concrete implementation steps.

Detected Capabilities

Trigger Keywords

Phrases that agents use to match this skill to user intent.

Use Cases

• Plan database schema migrations with rollback capability
• Coordinate API contract changes across multiple services
• Execute gradual dependency upgrades with version compatibility
• Migrate configuration systems while supporting parallel operation
• Protocol transitions in distributed systems with rollback guarantees
• Data format upgrades with preservation and verification steps

Quality Notes

• Skill provides high-level strategic guidance but lacks concrete implementation patterns or examples
• No specific technology context — unclear whether this applies to relational databases, NoSQL, APIs, or all
• Missing edge cases: how to handle failed transitions mid-rollout, observer consistency during overlap, partial state corruption
• No mention of tooling or verification commands — agent lacks concrete 'how to verify' procedures
• Strong on principles but weak on operational details like checkpoint naming, state tracking, or observability signals
• No limitations documented — unclear scope boundaries (e.g., does this cover only schema or also data migration?)
• Guideline 'stop after requested stage passes' is vague — what defines stage completion?