api-deprecation

What problem does it solve?

Helps you retire an API surface safely by ensuring consumers get clear timelines, visible in-product deprecation signals, measurable usage telemetry, and a concrete migration path before removal.

Core Features & Use Cases

• Five-stage deprecation lifecycle: announce, mark, instrument, migrate, and remove with concrete schedules and guardrails to prevent “surprise breakage.”
• Standards-aligned deprecation signaling: apply RFC 8594 Sunset headers, Deprecation headers, and schema/doc markers so clients can detect the change.
• Migration + recovery playbooks: provides escalation for consumers who haven’t moved (brownouts, 410 Gone mechanics, allow-list extensions, and post-mortems), including special cases like schema field removal and behavior changes.

Quick Start

Use the api-deprecation skill to plan a v1-to-v2 sunset by specifying what to retire, who is affected, the announce-to-sunset window, the migration supports you will provide, and the telemetry and brownout mechanics you will run.