{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "escalation-note",
  "name": "Escalation note",
  "category": "Work",
  "summary": "Shorten an escalation to its impact, unresolved blocker, and specific decision request.",
  "use_cases": [
    "Blocked work escalations",
    "Service escalations",
    "Management decision requests"
  ],
  "word_count": 156,
  "url": "https://sho.rten.it/methods/escalation-note/",
  "instructions_url": "https://sho.rten.it/methods/escalation-note/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/escalation-note/SKILL.md",
  "json_url": "https://sho.rten.it/methods/escalation-note/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/escalation-note/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#escalation-note",
  "skill_name": "escalation-note",
  "skill_description": "Shorten an escalation to its impact, unresolved blocker, and specific decision request. Use for Blocked work escalations, Service escalations, Management decision requests.",
  "agents_md_url": "https://sho.rten.it/methods/escalation-note/AGENTS.md",
  "sources": [],
  "instructions": "Condense the supplied escalation draft for the person who can resolve its stated blocker. Use this when progress needs a specific decision or intervention, not for routine status reporting.\n\nOpen with the requested action, its recipient, and the decision deadline. State the current impact and what will happen if the deadline is missed, preserving uncertainty. Keep the affected scope, evidence, and work already attempted so the recipient does not repeat a failed route.\n\nDistinguish the underlying issue from the reason it needs escalation. Retain options and tradeoffs already supplied, including any interim workaround and its limits. Do not invent authority, assign blame, strengthen severity, or promise that an option will solve the problem.\n\nUse a short request followed by Impact, Blocker, and Options. Keep enough chronology to explain the current state, but remove correspondence history and emotional emphasis. An escalation note is a request; do not write as if the requested approval has already been given.",
  "example": {
    "before": "We need operations director Eve to decide by 15:00 UTC today whether to approve a temporary courier at an extra cost of GBP 180. The regular courier canceled today's pickup for the museum shop's 24 packed orders. Dispatch coordinator Jae asked the courier to reinstate it, but the courier confirmed there is no driver available today. The orders are due to leave today under the delivery dates already given to customers. If we miss the temporary courier's 15:00 booking cutoff, the orders will not leave until tomorrow and may arrive a day late. Shop collection is possible for four local customers if they choose it, but we have not asked them yet and it would not address the other 20 orders. Jae cannot approve the extra fee. The team has exchanged many messages about how frustrating the cancellation is.",
    "after": "Request: Eve, approve or decline the temporary courier's extra GBP 180 fee by 15:00 UTC today. Approval is pending.\n\nImpact: All 24 packed museum-shop orders are due to leave today. Missing the 15:00 booking cutoff delays dispatch until tomorrow and may delay arrival by a day.\n\nBlocker: Regular courier canceled; Jae's reinstatement request failed because no driver is available. Jae cannot approve the fee.\n\nOptions: Temporary courier, subject to approval; or shop collection if four local customers choose it. They have not been asked, and collection cannot cover the other 20 orders.",
    "context": "Canceled courier pickup escalation",
    "must_preserve": [
      "Eve approval/decline by 15:00 UTC today; GBP 180 extra fee; pending",
      "24 packed orders due today based on customer dates",
      "Missing cutoff dispatch tomorrow; arrival delay uncertain",
      "Canceled pickup, no driver, reinstatement tried",
      "Jae lacks authority",
      "Four unasked local customers may collect; remaining20 not covered"
    ],
    "omitted": [
      "Repeated frustration and message history"
    ],
    "kind": "illustrative"
  }
}