{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "incident-update",
  "name": "Incident update",
  "category": "Technical",
  "summary": "Reduce an active incident update to impact, response, and next checkpoint.",
  "use_cases": [
    "Status-page updates",
    "Operational incident channels"
  ],
  "word_count": 145,
  "url": "https://sho.rten.it/methods/incident-update/",
  "instructions_url": "https://sho.rten.it/methods/incident-update/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/incident-update/SKILL.md",
  "json_url": "https://sho.rten.it/methods/incident-update/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/incident-update/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#incident-update",
  "skill_name": "incident-update",
  "skill_description": "Reduce an active incident update to impact, response, and next checkpoint. Use for Status-page updates, Operational incident channels.",
  "agents_md_url": "https://sho.rten.it/methods/incident-update/AGENTS.md",
  "sources": [],
  "instructions": "Condense a supplied update about an incident that is still in progress. Write for people who need its current state. Use a postmortem method for completed causal analysis.\n\nLead with affected service, user impact, and current status. Then state the response in progress and the next supplied checkpoint. Use a timestamp and timezone when the update includes them. Separate a completed mitigation from an unverified recovery; improvement does not prove resolution.\n\nKeep affected regions or customer groups, measured scope, workarounds, and explicit uncertainty. Distinguish a suspected cause from a confirmed cause. Retain changes since the previous update when supplied, but remove repeated history and internal coordination details that do not affect readers.\n\nOutput a short status paragraph followed by Response and Next update lines when supported. Do not invent a restoration estimate, reduce the stated impact, or promise another update unless the source provides one.",
  "example": {
    "context": "Active checkout incident",
    "before": "At 14:20 UTC, we are continuing to monitor the checkout service in the EU region. Between 14:05 and 14:18 UTC, approximately 4% of checkout attempts returned errors. We disabled the new request-batching option at 14:18 UTC. Error rates have since returned to the normal baseline, but we have not yet confirmed that recovery is stable. The root cause is still being investigated. We plan to provide our next update at 14:40 UTC. The team remains on the incident call and is watching the dashboards.",
    "after": "14:20 UTC — EU checkout is under monitoring. About 4% of attempts failed from 14:05–14:18 UTC. Errors are back to baseline; stable recovery is not yet confirmed.\nResponse: New request-batching option disabled at 14:18 UTC. Root cause under investigation.\nNext update: 14:40 UTC.",
    "must_preserve": [
      "EU checkout; about 4% failures; 14:05–14:18 UTC",
      "Request batching disabled at 14:18 UTC",
      "Errors back to baseline; stable recovery unconfirmed",
      "Root cause under investigation",
      "Current update 14:20 UTC; next update 14:40 UTC"
    ],
    "omitted": [
      "Incident call attendance and dashboard monitoring detail"
    ],
    "kind": "illustrative"
  }
}