Summary

This skill provides high-level guidance for implementing safe, reversible data migrations across schema, API, configuration, and dependency changes. It emphasizes mapping current state, defining forward and rollback paths, preserving data, sequencing operations carefully, and verifying transitions — but lacks concrete procedures, examples, or integration guidance to operationalize these principles in practice.

Detected Capabilities

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

Use Cases

• Execute database schema migrations with rollback verification
• Coordinate API version transitions while maintaining mixed-version compatibility
• Perform dependency upgrades with backward compatibility proof
• Implement configuration migrations across distributed systems
• Plan multi-stage data transformations with explicit destructive authorization checkpoints

Quality Notes

• Principles are sound and well-sequenced (expand → migrate → verify → contract)
• No concrete examples, code templates, or tool integration instructions — guidance is abstract
• Does not specify how to verify old/new paths or measure compatibility windows
• No error handling or rollback execution procedures documented
• Audience unclear — skill assumes deep infrastructure/database knowledge but provides no runbook structure
• Missing guidance on testing strategy, canary deployments, or gradual rollout mechanics
• No integration with specific migration tools (Flyway, Alembic, db-migrate, Helm, etc.)
• Lacks decision tree for when each migration type (schema vs. API vs. config) applies