deprecation-and-migration

Name: deprecation-and-migration
Availability: InStock
Author: kevindree

Plan and execute deprecation and migration of legacy systems.

Updated May 3, 2026

Search Tags:#migration #deprecation #feature flags #legacy systems #strangler pattern #api sunset

Ready to run

npx skills add https://github.com/kevindree/geehoo-gateway --skill deprecation-and-migration-kevindree

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams retire outdated systems, APIs, and features without breaking consumers or creating hidden operational risk. It turns deprecation from a vague announcement into a structured migration process with clear ownership and verification.

Core Features & Use Cases

Replacement Planning: Decide whether a legacy system should be maintained, migrated, or fully removed.
Safe Migration Paths: Use advisory deprecation, compulsory deadlines, strangler routing, adapters, and feature flags to move users gradually.
Removal Readiness: Confirm zero active usage before deleting code, tests, documentation, and configuration.
Use Case: A team replacing an old payments API can map dependencies, ship a new service in parallel, migrate clients one by one, and then remove the legacy implementation confidently.

Quick Start

Ask the skill to create a migration plan for a legacy service, including the replacement strategy, rollout steps, verification checks, and final removal checklist.

Frequently Asked Questions about deprecation-and-migration

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

FAQPage Schema

How do I safely deprecate a legacy API without breaking active consumers?▼

To safely deprecate a legacy API, use advisory deprecation notices, set compulsory deadlines, and migrate consumers gradually using strangler routing and adapters before removing the old implementation. This structured migration process prevents breaking active consumers.

What is the strangler pattern and how does it help with legacy system migration?▼

The strangler pattern helps with legacy system migration by routing traffic incrementally to a new replacement service while the old system runs in parallel. This allows teams to migrate consumers one by one and verify usage before final removal.

How do I plan a complete migration and removal process for an outdated service?▼

Plan a complete migration by defining a replacement-first strategy, establishing rollout steps with feature flags, executing usage verification checks, and completing the final removal of legacy code, tests, documentation, and configuration once usage reaches zero.

When should I use feature flags for API sunset and migration rollouts?▼

Use feature flags for API sunset and migration rollouts when you need to move users to a new implementation gradually and safely. Feature flags enable incremental rollouts, allowing teams to route specific consumers to the replacement service while maintaining stability.

What should be included in a legacy code removal checklist?▼

A legacy code removal checklist should include confirming zero active usage, followed by the complete deletion of the old code, associated tests, documentation, and configuration. This ensures no hidden operational risk remains after migrating consumers.