What problem does it solve?
This Skill helps you remove outdated systems, APIs, or features without breaking consumers or leaving teams to absorb endless maintenance and risk.
Core Features & Use Cases
- Deprecation decision framework: Evaluate whether to keep, sunset, or replace based on unique value, consumer impact, replacement availability, and maintenance costs.
- Migration-first discipline: Ensure the replacement exists, is production-proven, and has documentation plus a concrete migration guide before any removal.
- Safe rollout patterns: Plan incremental migrations (one consumer at a time) using approaches like strangler-style parallel operation, adapters, or feature flags.
- Zombie code control: Identify unowned, unmaintained code and decide whether to assign ownership and maintain it or deprecate with tooling and support.
- Verification checklist: Confirm migration completeness via metrics/logs, remove old code and references, and retire notices only after active usage is zero.
Quick Start
Use the deprecation-and-migration skill to create a migration plan for removing an old feature by specifying the replacement, defining the migration steps, and verifying zero active usage before deletion.
