{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "deprecation-notice",
  "name": "Deprecation notice",
  "category": "Technical",
  "summary": "Shorten a retirement notice to affected users, dates, and replacement steps.",
  "use_cases": [
    "API retirement messages",
    "Feature deprecation notices"
  ],
  "word_count": 151,
  "url": "https://sho.rten.it/methods/deprecation-notice/",
  "instructions_url": "https://sho.rten.it/methods/deprecation-notice/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/deprecation-notice/SKILL.md",
  "json_url": "https://sho.rten.it/methods/deprecation-notice/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/deprecation-notice/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#deprecation-notice",
  "skill_name": "deprecation-notice",
  "skill_description": "Shorten a retirement notice to affected users, dates, and replacement steps. Use for API retirement messages, Feature deprecation notices.",
  "agents_md_url": "https://sho.rten.it/methods/deprecation-notice/AGENTS.md",
  "sources": [],
  "instructions": "Condense a supplied deprecation notice so affected users can see whether they must act and by when. Preserve the distinction between a warning, a scheduled removal, and an operation that already fails.\n\nLead with the retiring feature or interface and the affected users. Keep deprecation and removal dates, including timezones when supplied. State the replacement and the minimum documented migration step. Preserve differences in replacement behavior, compatibility periods, and exceptions that could change a user's plan.\n\nRemove organizational history, repeated encouragement, and reasons that do not affect the decision. Retain a reason when it explains a constraint, such as a protocol incompatibility. Keep exact names, paths, version numbers, and supplied migration links.\n\nOutput a short notice with Affected, Deadline, and Action when useful. Do not invent a grace period, assume that all users are affected, call the replacement equivalent without evidence, or imply that removal has happened before its stated date.",
  "example": {
    "context": "Export API retirement",
    "before": "The GET /v1/exports endpoint is now deprecated for clients that download CSV exports. It will continue to work until it is removed on October 1, 2026 at 00:00 UTC. Clients should move to POST /v2/export-jobs before that time. Unlike the old synchronous endpoint, the replacement creates an asynchronous job, so clients must poll the returned status_url and download the file when the job is ready. Existing export files remain downloadable for their usual seven-day retention period. JSON exports use a different endpoint and are not affected by this change.",
    "after": "Affected: CSV clients using deprecated GET /v1/exports. JSON exports are unaffected.\nDeadline: Removal on October 1, 2026, 00:00 UTC; the old endpoint works until then.\nAction: Switch to POST /v2/export-jobs. Poll status_url, then download when ready; the replacement is asynchronous.\nExisting files retain their seven-day download window.",
    "must_preserve": [
      "GET /v1/exports deprecated for CSV; JSON unaffected",
      "Works until removal October 1, 2026 at 00:00 UTC",
      "Replace with POST /v2/export-jobs before removal",
      "Replacement asynchronous; poll status_url then download when ready",
      "Existing files retain usual seven-day availability"
    ],
    "kind": "illustrative",
    "omitted": [
      "Repeated references to clients and the old endpoint."
    ]
  }
}