skills.rest
pyoclaw
pyoclawCOMMUNITY
Explore all skills by this author →
GitHub

deprecation-and-migration

Plan structured deprecation and migration phases for APIs, services, and features.

Updated Aug 27, 2026
Search Tags:#migration#deprecation#lifecycle#risk-management#adapter-pattern#strangler-pattern
One-click install
npx skills add https://github.com/pyoclaw/agent-skills --skill deprecation-and-migration-pyoclaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deprecation-and-migration
Source: https://github.com/pyoclaw/agent-skills/tree/main/skills/deprecation-and-migration
Command: npx skills add https://github.com/pyoclaw/agent-skills --skill deprecation-and-migration-pyoclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams identify when to deprecate or migrate components, plan migrations, and communicate changes to stakeholders to reduce risk and maintenance costs.

Core Features & Use Cases

  • Structured deprecation decision framework to assess value, users, and replacement.
  • Migration patterns and step-by-step approach such as Strangler, Adapter, and feature-flag migrations.
  • Lifecycle guidance from planning to removal, including how to migrate consumers and manage zombie code.

Quick Start

Draft a deprecation plan and migration guide for a legacy API to guide teams through safe sunset and replacement.

Frequently Asked Questions about deprecation-and-migration

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

FAQPage Schema
How do I plan a safe API migration and deprecate the old version?▼

The Strangler pattern manages safe migrations by incrementally replacing legacy system functionality with new implementations. It allows teams to migrate consumers gradually, reducing risk by running old and new systems in parallel until full replacement is achieved.

When should I deprecate legacy services and what lifecycle phases are involved?▼

Deprecate legacy services when maintenance costs outweigh value and a viable replacement exists. The lifecycle involves planning, consumer communication, phased migration, and final removal to manage sunset decisions and eliminate zombie code.

What is the best way to manage risk during a system migration?▼

The best way to manage migration risk is through structured risk assessment and governance guidance. Apply feature-flag migrations or the Adapter pattern to control rollouts, enabling safe fallbacks and minimizing consumer disruption.

How do I communicate a deprecation plan to stakeholders for a legacy feature?▼

Communicate a deprecation plan by drafting a structured migration guide detailing sunset decisions, replacement features, and transition timelines. This reduces stakeholder uncertainty and helps teams manage consumer expectations effectively.

How do I remove zombie code after a feature migration is complete?▼

Remove zombie code by completing the final lifecycle phase of the deprecation process, ensuring all consumers have migrated to the new implementation. Governance guidance verifies safe removal without disrupting active services.

Related Skills

Explore More Software Engineering Skills→
reez455Greez455G

deprecation-and-migration

Plan deprecation and migration strategies for codebases, systems, and APIs.

Community
Advanced
williamzujkowskiwilliamzujkowski
17

legacy-bridge

Translate legacy @load patterns into Load: skills/* format with deprecation warnings.

Community
Intermediate
djinilabsdjinilabs
8

PostHog Feature Flags

Manage PostHog feature flags for A/B testing and gradual rollouts.

Official
Intermediate
calvyntwhcalvyntwh

occams-razor

Remove unnecessary code and abstractions after verifying references and running tests.

Community
Intermediate