Deprecation and migration
Skill charlieviettq/awesome-agent-skill/.cursor/skills/core-workflow/deprecation-and-migration
Plan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules. Triggers: "deprecate", "migration plan", "sunset", "remove legacy", "strangler".From its SKILL.md
npx -y skills add charlieviettq/awesome-agent-skill --skill deprecation-and-migrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 24 stars24 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 241 tokens by cl100k_base, as published. Nobody here has run it
Deprecation and migration
Decision questions
- Does the old system still provide unique value?
- How many consumers? Migration cost each?
- Is replacement production-proven?
- Cost of NOT deprecating (security, maintenance)?
Compulsory vs advisory
| Type | When |
|---|---|
| Advisory | Stable legacy, optional migration |
| Compulsory | Security risk, blocks progress — need tooling + deadline |
Default advisory unless risk justifies force.
Process
- Build replacement first
- Announce — status, replacement, migration guide, timeline
- Migrate consumers incrementally; owner migrates users when possible
- Remove only after zero active usage verified
Patterns
| Pattern | Use when |
|---|---|
| Strangler | Gradual traffic shift |
| Adapter | Old interface, new implementation |
| Feature flag | Per-consumer or cohort cutover |
Zombie code signals
- No maintainer, active dependents, failing tests ignored, stale deps
Output
Deprecation notice + migration steps + removal checklist.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.