addy-deprecation-and-migration

Coordinate deprecation plans and migrations across software systems.

Updated Mar 19, 2026

Search Tags:#planning #migration #deprecation #governance #legacy-code #migration-guides #sunset

Ready to run

npx skills add https://github.com/japurcell/skills --skill addy-deprecation-and-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: addy-deprecation-and-migration
Source: https://github.com/japurcell/skills/tree/main/skills/addy-deprecation-and-migration
Command: npx skills add https://github.com/japurcell/skills --skill addy-deprecation-and-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecation and migration are complex, costly processes; this skill provides a structured approach to sunset legacy systems and migrate users safely.

Core Features & Use Cases

Provides decision criteria and governance for deprecation (planning, replacement evaluation, migration tooling).
Guides across Strangler pattern, adapters, and feature flags.
Use cases include sunsetting an API, migrating users to a new service, or consolidating duplicate implementations.

Quick Start

Define a deprecation plan for a legacy API and execute a migration path to the replacement.

Frequently Asked Questions about addy-deprecation-and-migration

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

FAQPage Schema

How do I plan a legacy API deprecation and migration safely?▼

Legacy API deprecation requires structured governance to plan, evaluate replacements, and execute a safe migration path for users. You define decision criteria, build migration tooling, and apply sunset strategies to ensure the new implementation is production-ready before shutting down the old system.

What is the Strangler pattern and when should I use it for system migration?▼

The Strangler pattern is a migration strategy that gradually replaces legacy components by routing functionality to new implementations. Use it when sunsetting an API or consolidating duplicate implementations, allowing safe transition without a risky big-bang rewrite.

What's the best way to migrate users to a replacement service?▼

Migrating users to a replacement service is best handled by combining feature flags, adapters, and migration guides. This structured approach provides governance and tooling to ensure the new service handles production traffic safely before the old system is sunset.

How do I write migration guides for consolidating duplicate implementations?▼

Migration guides for consolidating duplicate implementations must document the sunset strategy, replacement evaluation criteria, and step-by-step transition paths. They provide governance and tooling to ensure replacements are production-ready and old systems are safely sunset.

Does this deprecation approach work for sunsetting APIs across an organization?▼

Deprecation and migration governance applies to planning, documenting, and executing sunset strategies across organizations. It supports sunsetting APIs, migrating users to new services, and consolidating duplicate implementations by providing structured tooling and replacement evaluation.

When should I not use a gradual migration approach for legacy code?▼

A gradual migration approach using adapters or feature flags may not suit legacy code when replacements cannot achieve production-ready status or when governance criteria for safely sunsetting the old system are not met. Ensure the new implementation handles all required functionality before proceeding.