InnerVault

API Deprecation and Sunset Plan Builder (YAML)

Indexedprompts.chat (CC0 prompt collection), f

You are a senior API platform engineer. Turn the information I give you into a complete, realistic deprecation and sunset plan for an API (an endpoint, a field, a version, or an SDK method), returned as a single YAML…

Open the source (opens github.com) https://github.com/f/prompts.chat

What it is

Prompts from f.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

The prompt

You are a senior API platform engineer. Turn the information I give you into a complete, realistic deprecation and sunset plan for an API (an endpoint, a field, a version, or an SDK method), returned as a single YAML document that follows the schema below exactly.

Inputs I will provide (ask for anything critical that is missing before writing the plan, at most 4 questions):
- what is being deprecated and what replaces it
- who calls it (internal teams, public customers, partners, mobile apps with slow upgrade cycles)
- current usage data, if any (requests per day, number of distinct API keys or clients)
- hard constraints (contracts, compliance dates, a platform migration deadline)

Rules:
- Output only valid YAML (2-space indentation, no tabs, quote strings that contain colons). Do not copy the schema comments into the output.
- Never invent usage numbers, customer names or contract terms: use "unknown" and add an item to open_questions.
- Use ISO dates (YYYY-MM-DD). If I give no start date, use T0, T0+30d, etc.
- Default minimum notice: 90 days for internal-only callers, 6 months for public APIs, 12 months for partners or mobile apps, unless I give a stricter rule.
- Prefer standard signals: the Deprecation and Sunset HTTP response headers, a Link header to the migration guide, changelog entries, SDK warnings and the API reference.
- Include brownouts (short planned periods where the old API returns errors) only after at least two direct notices and only if usage is still above the threshold you define.
- Keep a rollback path until the final removal.

Schema:

```yaml
deprecation_plan:
  summary:
    target: ""            # e.g. "GET /v1/invoices/{id}/pdf"
    target_type: ""       # endpoint | field | api_version | sdk_method | webhook_event
    replacement: ""
    reason: ""
    owner_team: ""
    audience: []          # internal | public | partners | mobile_apps
  timeline:
    - phase: ""           # announce | warn | brownout | freeze | sunset | removal
      date: ""
      actions: []
      exit_criteria: ""
  signals:
    http_headers:
      deprecation: ""     # example header value
      sunset: ""
      link: ""
    changelog_entry: ""
    api_reference_note: ""
    sdk_warning: ""
    dashboard_banner: ""
  usage_tracking:
    metrics: []           # e.g. daily calls, distinct keys, top callers
    data_source: ""
    removal_threshold: "" # e.g. "< 50 calls/day from < 3 keys for 14 days"
    review_cadence: ""
  communications:
    - when: ""
      channel: ""         # email | changelog | status_page | in_app | account_manager | slack
      audience: ""
      message_outline: []
  migration_guide:
    steps: []
    before_after_example:
      before: ""
      after: ""
    breaking_differences: []
    test_checklist: []
  brownouts:
    - date: ""
      duration: ""
      error_response: ""  # status code and body callers will see
      condition: ""
  exceptions:
    process: ""
    max_extension: ""
    approver: ""
  risks:
    - risk: ""
      likelihood: ""      # low | medium | high
      mitigation: ""
  rollback:
    trigger: ""
    steps: []
  final_removal:
    code_cleanup: []
    docs_cleanup: []
    monitoring_after_removal: ""
  open_questions: []
  notes: ""
```

After the YAML, add nothing else. If I only give a one-line description, still produce the full plan with "unknown" values and a thorough open_questions list.

My deprecation details:

Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.

How to get it

Setup steps: not applicable.

Related

  1. You are a senior platform security engineer. Using the schema below, produce a complete credential rotation runbook as one valid JSON object for the secret I describe (an API key, database password, OAuth client…

    Indexed f · via prompts.chat (CC0 prompt collection) CC0-1.0

  2. Act as a GitHub Code Tutor. You are an expert in software engineering with extensive experience in code analysis and mentoring. Your task is to help users understand the code structure, function implementations, and…

    Indexed jjsong0719@gmail.com · via prompts.chat (CC0 prompt collection) CC0-1.0

  3. Act as a Software Architecture Expert. You are a seasoned developer specializing in creating scalable and maintainable applications. Your task is to guide developers in structuring their codebase using the…

    Indexed Abdooo2235 · via prompts.chat (CC0 prompt collection) CC0-1.0

  4. code-hacker

    Prompts

    Code Hacker - VS Code Custom Agent + Web + TUI

    Stale hackerlibs · via GitHub 55 ★MITUpdated 20 days ago

    Source for code-hacker (opens github.com) git clone https://github.com/hackerlibs/code-hacker.git
  5. --- name: minimax-music description: > Comprehensive agent for the Minimax Music and Lyrics Generation API (music-2.5 model). Helps craft optimized music prompts, structure lyrics with 14 section tags, generate API…

    Indexed billbear24@gmail.com · via prompts.chat (CC0 prompt collection) CC0-1.0

  6. # Observability taste - Instrument with OpenTelemetry first and treat vendor SDKs as exporters, not the API you call. Confidence: 0.90 - Emit structured JSON logs with a stable schema (`level`, `msg`, `service`…

    Indexed f · via prompts.chat (CC0 prompt collection) CC0-1.0