deprecation-and-migration

Automate deprecation and migration of systems, APIs, or features.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions --skill deprecation-and-migration-tgmarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deprecation-and-migration
Source: https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions/tree/main/upstream-snapshots/agent-skills/skills/deprecation-and-migration
Command: npx skills add https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions --skill deprecation-and-migration-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of deprecating old systems, APIs, or features and migrating users to new ones, reducing the overhead and risks associated with these transitions.

Core Features & Use Cases

  • Deprecation Decision-Making: Provides a structured approach to decide whether to deprecate or maintain a system, considering factors like unique value, user dependencies, and migration cost.
  • Migration Process: Offers a step-by-step guide for migrating users from the old system to the new one, including building the replacement, announcing the change, and incrementally migrating users.
  • Migration Patterns: Includes patterns like the Strangler Pattern and Adapter Pattern to handle migration scenarios effectively.
  • Zombie Code Management: Identifies and addresses zombie code, ensuring that no code remains unused and unmanaged.
  • Common Rationalizations: Debunks common reasons for not deprecating or migrating, providing evidence-based arguments for change.

Quick Start

Use the deprecation-and-migration skill to assess the deprecation and migration of an old system, 'LegacySystem', to a new system, 'NewSystem'.

Frequently Asked Questions about deprecation-and-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deprecate an old API and migrate users to a new system?

To deprecate an old API and migrate users, you need a structured migration process that includes deciding whether to deprecate, building the replacement, announcing the change, and incrementally migrating users to the new system.

What is the Strangler Pattern for system migration?

The Strangler Pattern is a migration strategy that incrementally replaces a legacy system by building the new system alongside it, gradually routing users to the new functionality until the old system is fully deprecated.

How do I decide whether to deprecate or maintain a legacy system?

Deciding whether to deprecate a legacy system requires evaluating its unique value, user dependencies, and migration cost, while debunking common rationalizations for not deprecating to provide evidence-based arguments for change.

What is the best way to handle zombie code during a feature migration?

The best way to handle zombie code during a feature migration is to identify and address it systematically, ensuring that no unused and unmanaged code remains after the system deprecation and user transition are complete.

When should I use the Adapter Pattern for API migration?

You should use the Adapter Pattern for API migration when you need to handle migration scenarios by bridging the interface between the old deprecated system and the new replacement, allowing users to transition incrementally.

Does system migration require understanding user dependencies?

Yes, system migration requires a thorough understanding of user dependencies and system architecture to ensure a structured approach to decision-making, migration planning, and execution without disrupting existing services.