skills.rest
j-cogburn
j-cogburnCOMMUNITY
Explore all skills by this author →
GitHub

deprecation-and-migration

Create deprecation and migration plans for legacy systems and APIs.

Updated Jun 1, 2026
Search Tags:#migration#technical debt#deprecation#legacy code#api sunset#zombie code#system retirement
One-click install
npx skills add https://github.com/j-cogburn/d3 --skill deprecation-and-migration-j-cogburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deprecation-and-migration
Source: https://github.com/j-cogburn/d3/tree/main/tests/project-t01/.d3/skills/deprecation-and-migration
Command: npx skills add https://github.com/j-cogburn/d3 --skill deprecation-and-migration-j-cogburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often struggle to safely remove outdated code, APIs, and features without breaking user workflows, leading to accumulating technical debt, unpatched security vulnerabilities in unmaintained legacy systems, and wasted engineering time on low-value maintenance tasks.

Core Features & Use Cases

  • Structured Deprecation Decision Framework: Evaluate whether to maintain or retire a system using a 5-question assessment that weighs user impact, ongoing maintenance cost, and replacement availability.
  • Incremental Migration Patterns: Implement proven patterns like the Strangler Pattern, Adapter Pattern, and feature flag rollouts to move users from old to new systems with zero downtime.
  • Zombie Code Management: Identify and address unowned, unmaintained code that poses security risks, with clear steps to either assign ownership or deprecate it with a concrete migration plan.
  • Use Case Example: Use this skill to sunset a legacy authentication API, build a step-by-step migration guide for downstream consumers, and verify zero active usage before removing the old code entirely.

Quick Start

Use the deprecation-and-migration skill to create a full deprecation and migration plan for the legacy inventory management system that is being replaced by the new cloud-based tool.

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 consumer workflows?▼

To safely deprecate a legacy API, use a structured decision framework to assess user impact and apply incremental migration patterns like the Strangler Pattern to move active consumers to the new replacement system with zero downtime.

What is the best way to migrate users from outdated system implementations to newer replacements?▼

The best way to migrate users from outdated implementations is using incremental migration patterns like Adapter Patterns and feature flag rollouts, ensuring a seamless transition to the new replacement system without disrupting active workflows.

How do I evaluate whether to maintain or retire unowned zombie code?▼

Evaluate whether to maintain or retire unowned zombie code using a 5-question assessment framework that weighs ongoing maintenance cost, user impact, and replacement availability to determine if the unmaintained code should be assigned ownership or deprecated.

Can I use feature flag rollouts to sunset unused functionality and reduce technical debt?▼

Yes, you can use feature flag rollouts as an incremental migration pattern to safely sunset unused functionality, allowing you to verify zero active usage and reduce accumulated technical debt before removing the old code entirely.

When should I use the Strangler Pattern for legacy system retirement?▼

Use the Strangler Pattern for legacy system retirement when you need to incrementally migrate users from old APIs to newer replacements with zero downtime, ensuring deprecation is completed without breaking active consumer workflows or introducing security risks.

Related Skills

Explore More Software Engineering Skills→
epicsagasepicsagas
1

system-diet

Inventory and remove 20% of active tools, plugins, and automation pipelines.

Community
Advanced
mymx2mymx2
4

deprecation-and-migration

Plan deprecation and migration of legacy systems with zero active usage verification.

Community
Advanced
Handy369Handy369

deprecation-and-migration

Plan deprecation and migration for legacy systems with adapters or feature flags.

Community
Intermediate
fanguyunfanguyun

legacy-modernizer

Design incremental migration strategies and generate API facade designs for legacy systems.

Community
Advanced