← ClaudeAtlas

deprecation-and-migrationlisted

Plan or implement a safe API, feature, data, or schema migration. Use when retiring a live contract; not for ordinary code cleanup.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# Deprecation and Migration Move consumers from an existing contract to a replacement without assuming removal is safe. Adapted from Addy Osmani's `deprecation-and-migration` workflow; see the bundled license and repository third-party notice. ## Route precisely - Use for replacing or retiring a live API, feature, dependency, stored shape, or database schema with possible consumers. - Use `code-simplification` for behavior-preserving local refactors and `code-review` for a read-only diff review. Use `vet-dependency` when the central decision is whether a replacement package meets the project's contract. - A request for a plan permits planning and read-only inspection; execution of destructive or external steps follows the user's authorization and repository rules. ## Inventory the contract 1. Read repository instructions, current state, migration history, deployment topology, and declared compatibility promises. 2. Identify producers, consumers, stored data, public routes or symbols, operational jobs, and usage evidence. Search plausible alternate paths before declaring a consumer absent. Mark inaccessible downstream consumers unknown. 3. State what the replacement preserves, changes, or intentionally drops. Identify whether old and new versions must coexist during rollout. ## Design the transition 1. Choose phases that keep each deployed combination valid. For schemas, consider expand, backfill, switch readers and writers, then contract; use a different sequence when