Skip to content
Development
Skill

/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.

From plugin
awesome-agent-skill
26200 skills4 commands
Install
$ npx -y skills add charlieviettq/awesome-agent-skill --skill deprecation-and-migration --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/deprecation-and-migration

Context preview

The summary Claude sees to decide when to auto-load this skill.

Plan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules.

SKILL.md

deprecation-and-migration.SKILL.md
name: deprecation-and-migration
description: "Plan deprecation and migration—replacement first, consumer migration, strangler and adapter patterns, zombie code removal. Use when sunsetting APIs, libraries, or legacy modules."
allowed-tools: Read, Glob, Grep

Deprecation and migration

Decision questions

1. Does the old system still provide unique value? 2. How many consumers? Migration cost each? 3. Is replacement production-proven? 4. 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

1. **Build replacement** first 2. **Announce** — status, replacement, migration guide, timeline 3. **Migrate consumers** incrementally; owner migrates users when possible 4. **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.

Ships withawesome-agent-skill

Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).

Get the whole plugin

Other skills on awesome-agent-skill.