deprecation-and-migration

Generate migration plans for legacy APIs with database schema evolution strategies.

Updated Apr 19, 2026

Search Tags:#refactoring #migration #deprecation #system-design #legacy-code #technical-debt

Ready to run

npx skills add https://github.com/dmarins/sdd --skill deprecation-and-migration-dmarins

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the technical debt and operational burden caused by maintaining obsolete systems, APIs, or features that no longer provide sufficient value.

Core Features & Use Cases

Lifecycle Management: Provides a structured framework for deciding when to deprecate versus maintain legacy systems.
Migration Patterns: Implements proven strategies like the Strangler Pattern, Adapter Pattern, and Expand/Contract database migrations to ensure zero-downtime transitions.
Use Case: Use this skill when you need to replace a legacy API with a new version while ensuring all existing consumers are migrated safely without breaking production traffic.

Quick Start

Use the deprecation-and-migration skill to generate a migration plan for the legacy task service including a strategy for database schema evolution.

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 migrate a legacy API to a new version without breaking production traffic?▼

To migrate a legacy API safely, this skill applies structured frameworks for deprecation and migration, ensuring incremental rollout and operational continuity. It uses proven strategies like the Strangler Pattern to replace legacy code without downtime.

What is the best way to handle database schema refactoring during a system decommissioning?▼

Database schema refactoring during system decommissioning is handled using Expand/Contract migration patterns. This ensures safe database schema evolution and zero-downtime transitions while migrating consumers away from the legacy system.

When should I deprecate legacy code versus maintain it?▼

You should deprecate legacy code when the technical debt and operational burden of maintaining obsolete systems outweigh their value. This skill provides a structured lifecycle management framework to evaluate and decide when to decommission legacy systems.

How do I generate a migration plan for retiring legacy system components?▼

Generating a migration plan for retiring legacy system components involves applying structured frameworks for risk mitigation and safe migration. The skill systematically maps out component lifecycle management and operational continuity during code removal.

Does this approach work for zero-downtime transitions during API versioning?▼

Yes, this approach supports zero-downtime transitions during API versioning by implementing the Adapter Pattern and Strangler Pattern. These migration patterns ensure operational continuity while incrementally rolling out replacements for legacy systems.