Stats
Actions
Tags
From api-expert
Execute the API deprecation and sunset workflow per RFC 9745 (Deprecation header) and RFC 8594 (Sunset header). Plans the notice period (12-24 months typical), writes migration guide, adds `Deprecation` + `Sunset` response headers with Link to migration docs, marks `deprecated: true` in OpenAPI spec and `@deprecated` in GraphQL SDL, notifies consumers (email + dashboard + changelog + blog), tracks usage telemetry to identify heavy users, and enforces the sunset with HTTP 410 Gone at the agreed date. Triggers on "deprecate this endpoint", "sunset v1", "retire the old api", "remove a field", "mark as deprecated", "plan a sunset". Produces a complete deprecation rollout.
How this skill is triggered — by the user, by Claude, or both
Slash command
/api-expert:deprecate-apiThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Dispatches the api-expert agent with a deprecation briefing.
Dispatches the api-expert agent with a deprecation briefing.
| Info | Why |
|---|---|
| What's deprecating (endpoint / field / version / whole API) | Scope |
| Replacement (if exists) | Required in migration guide |
| Consumer audience (internal only / external partners / public) | Determines notice period |
| Target sunset date (absolute date, RFC 1123 format) | Must be >= 12 months for external (>= 24 months is GitHub-style best practice) |
| Current usage telemetry available? | Can we identify heavy users to notify directly? |
Agent({
description: "API deprecate: <what>",
subagent_type: "api-expert:api-expert",
model: "opus",
prompt: "<see briefing below>"
})
ORIGINAL USER REQUEST: <verbatim>
WORKFLOW: deprecation
WHAT: <endpoint / field / version / whole API>
REPLACEMENT: <path to new or "none — being removed">
AUDIENCE: <internal / external partners / public>
SUNSET DATE (target): <ISO date>
TELEMETRY: <yes / no, what's tracked>
Read ${CLAUDE_PLUGIN_ROOT}/references/documentation-lifecycle.md FIRST.
DELIVERABLES:
1. Deprecation plan with dates (announcement, deprecation active, sunset, hard cutoff)
2. HTTP headers (RFC 9745 Deprecation + RFC 8594 Sunset)
3. OpenAPI spec update (deprecated: true + x-sunset)
4. GraphQL SDL update (@deprecated directive) if applicable
5. Code-level deprecation markers
6. Changelog entry
7. Migration guide document
8. Communication plan
9. Usage telemetry to set up
10. Enforcement after sunset (410 Gone + RFC 9457 body)
11. Internal cleanup plan (after grace period)
PROCEED.
Present the timeline + all code diffs + migration guide draft. User approves + schedules the announcement.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub themizeguy/api-expert-public