skills.rest
ByronWilliamsCPA
ByronWilliamsCPAOFFICIAL
Explore all skills by this author →
GitHub

deprecation-and-migration

Plan safe deprecation and migration of outdated systems and APIs.

Updated Nov 24, 2025
Search Tags:#migration#technical debt#deprecation#legacy code#strangler pattern#zombie code#system sunset
One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill deprecation-and-migration-byronwilliamscpa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deprecation-and-migration
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/deprecation-and-migration
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill deprecation-and-migration-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often struggle to safely remove outdated systems, APIs, and features without disrupting users, while unmaintained legacy code accumulates security risks and technical debt that slows down development.

Core Features & Use Cases

  • Structured Deprecation Decision Framework: Guides teams to evaluate whether a system should be maintained or deprecated, quantify migration scope, and weigh maintenance costs against removal effort.
  • Proven Migration Patterns: Implements industry-standard patterns including the strangler pattern, adapter pattern, and feature flag migrations to move users from old to new systems incrementally with zero downtime.
  • Zombie Code Remediation: Helps identify unowned, unmaintained legacy code with active consumers, and provides actionable steps to either assign proper ownership or deprecate it with a concrete migration plan.
  • Use Case: For example, if your team is replacing a legacy customer data API, use this skill to plan a 3-month deprecation timeline, roll out the new API to 10% of users via feature flags, and fully remove the old API once all traffic is migrated.

Quick Start

Ask the AI to create a full deprecation and migration plan for your legacy inventory management system, including a timeline, user communication template, and incremental rollout strategy using feature flags.

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 disrupting active users?▼

Safely deprecate a legacy API by applying the strangler pattern and feature flag migrations to incrementally route traffic to the new system with zero downtime. This approach provides a structured timeline and post-deprecation verification to eliminate user disruption.

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

The strangler pattern is a proven migration technique that incrementally replaces legacy functionality by routing traffic to a new system until the old one is fully retired. Use it to execute low-risk, end-to-end system replacements without forcing downtime.

How do I remediate zombie code that has active consumers but no clear owner?▼

Remediate zombie code by identifying the unowned, unmaintained legacy components and their active consumers, then taking actionable steps to either assign proper ownership or execute a concrete deprecation and migration plan to eliminate technical debt.

What's the best way to plan a feature sunset and consolidate duplicate implementations?▼

The best way to plan a feature sunset is to apply a structured deprecation decision framework to quantify migration scope, weigh maintenance costs against removal effort, and use adapter patterns for consolidating duplicate implementations while reducing technical debt.

Can I use this approach to replace a legacy inventory management system with a phased rollout?▼

Yes, you can replace a legacy inventory management system by creating a full deprecation timeline, rolling out the new system to a subset of users via feature flags, and fully removing the old system once all traffic is successfully migrated.

When should I not use an incremental migration pattern for retiring technical debt?▼

You should reconsider incremental migration patterns if your deprecation decision framework reveals that the migration scope is trivial or maintenance costs are negligible, making a direct system replacement faster and more cost-effective than a phased rollout.

Related Skills

Explore More Software Engineering Skills→
erichowenserichowens
181

code-necromancer

Map legacy codebases through archaeology, resurrection, and rejuvenation phases.

Community
Advanced
santanapolsantanapol

deprecation-and-migration

Plan and execute legacy system retirement with incremental user migration.

Community
Advanced
NVIDIA-NeMoNVIDIA-NeMo
58

deploy-sandbox

Deploy NAT agents as isolated OpenShell sandboxes with Landlock filesystem protection.

Official
Advanced
DauQuangThanhDauQuangThanh
14

application-migration

Plan and manage application migrations from legacy systems to modern platforms.

Community
Advanced