What problem does it solve? Retiring an API, library, feature, or schema without breaking consumers is risky: hidden callers, destructive schema changes, and irreversible data loss can turn a simple cleanup into an outage. This Skill provides a structured workflow for deprecating old behavior and migrating consumers safely, with evidence-based verification before removal. ## Core Features & Use Cases - Consumer Inventory and Impact Analysis: Maps all callers, integrations, configurations, and runtime consumers using static search combined with tests, telemetry, logs, and owner confirmation. - Reversible Cutover Patterns: Guides selection of adapters, strangler patterns, feature flags, compatibility layers, and the expand-migrate-contract approach for schema changes. - Incremental Migration with Approval Gates: Migrates consumers in thin slices with verification at each step, and pauses for explicit approval before changing public contracts, production data, or destructive state. - Use Case: You need to retire a legacy REST endpoint used by multiple services. The Skill helps you inventory consumers, publish a migration guide with a support window, move each consumer with rollback evidence, and remove the old code only after verifying zero active usage. ## Quick Start Ask the assistant to plan the deprecation of the legacy v1 payments API and migrate all consumers to v2 with a reversible cutover strategy.
