skills.rest
vtgiang-dotcom
vtgiang-dotcomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

deprecation-and-migration

Deprecate legacy APIs and plan migration to replacement implementations.

3|Updated Apr 1, 2026
Search Tags:#planning#migration#deprecation#governance#risk-management#legacy#sunset
One-click install
npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill deprecation-and-migration-vtgiang-dotcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deprecation-and-migration
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/deprecation-and-migration
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill deprecation-and-migration-vtgiang-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecate old systems and guide safe migration to newer implementations, reducing maintenance costs and risk.

Core Features & Use Cases

  • Deprecation decision framework and governance guidelines.
  • Migration planning patterns (Strangler, Adapter, feature flags) with actionable steps.
  • Sunset readiness verification to ensure all consumers are migrated or properly transitioned.

Quick Start

Outline a deprecation plan and start migrating users to the replacement using the migration guide.

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 migration and deprecation for legacy APIs?▼

A sunset readiness check verifies that all consumers are migrated or properly transitioned before final removal. It provides the governance documentation needed to confirm legacy API deprecation is complete and risk-free.

What is the best way to deprecate old systems without breaking consumers?▼

Migration planning patterns like Strangler, Adapter, and feature flags provide actionable steps for incremental replacement. They enable phased rollout of newer implementations while legacy modules remain operational during the transition.

How do I document governance requirements for legacy feature removal?▼

Documenting governance requirements for legacy feature removal involves recording deprecation decisions and sunset readiness verifications. This satisfies compliance needs by proving all consumers are properly transitioned before final shutdown.

When should I use feature flags instead of the Strangler pattern for module migration?▼

Use feature flags for module migration when you need to toggle between old and new implementations dynamically for specific users. Use the Strangler pattern when incrementally replacing legacy functionality endpoint by endpoint without runtime toggles.

What are the limitations of using feature flags for legacy system deprecation?▼

Feature flags for legacy system deprecation introduce technical debt if not cleaned up post-migration and add runtime overhead. They are less suitable for permanent architectural changes compared to the Strangler pattern's clean incremental replacement.

Related Skills

Explore More Software Engineering Skills→
Marwan78888Marwan78888
16

spec-miner

Reverse-engineer codebases into EARS-formatted specifications using Read, Grep, and Glob.

Community
Intermediate
GoBeromsuGoBeromsu
2

deprecation-and-migration

Plan deprecation and migration with replacement plans and removal criteria.

Community
Advanced
emilneuraz-aiemilneuraz-ai

istio-traffic-management

Configure Istio VirtualService, DestinationRule, Gateway, and ServiceEntry resources for routing and resilience.

Community
Advanced
celticht32celticht32
4

couchbase-migration-execution

Plan and execute data migrations into Couchbase from operational sources.

Community
Advanced