API Versioning Deprecation Review

Use this skill to convert API versioning, deprecation, breaking change, SDK, migration, changelog, and customer-notification questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

1. Identify API surface, consumers, current versions, change type, compatibility impact, SDK/docs impact, usage analytics, contractual promises, and migration deadline.
2. Read references/api-versioning-deprecation-patterns.md.
3. Classify change as additive, behavior change, breaking schema, auth/permission, rate limit, webhook, SDK-only, deprecated field, endpoint sunset, or emergency security change.
4. Define versioning policy, compatibility tests, docs/changelog, migration guide, usage segmentation, notification plan, exception path, and support runbook.
5. Produce API change plan, state machine, decision table, event schema, deprecation checklist, and rollout timeline.

When not to use

• Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails