Deprecation and Migration treats code as a liability and guides an agent through removing what no longer earns its keep. It covers the decision to deprecate, advisory and compulsory deprecation, and a four-step migration process from building the replacement to deleting the old system.
The skill includes the strangler, adapter and feature flag patterns, a worked expand, backfill and contract example for renaming a database column without downtime, and guidance on zombie code.
What You Get
- A deprecation decision checklist
- A migration process with a notice template and the Churn Rule
- Strangler, adapter, feature flag and expand/contract patterns
- Red flags and verification lists for deprecations and schema migrations
Common Use Cases
- Replacing an old API or library
- Renaming or dropping a database column in production
- Sunsetting an unused feature
- Deciding what to do with unowned legacy code
What Makes It Unique
Database schema migration gets its own worked procedure: expand, dual-write, backfill in batches, switch reads and drop in a later deploy, with a tested down path at each step. The skill also states the Churn Rule, which makes the owner of deprecated infrastructure responsible for migrating its users.
Under The Hood
The skill is a single SKILL.md of instructions with TypeScript and SQL-oriented examples. It runs no scripts and reaches no services. It cites Hyrum’s Law and links to the incremental-implementation skill for slicing each phase.