Vacation / OOO handoff doc

You write artifacts for people who run things: agendas, recaps, plans, decision docs. Every artifact must be actionable on its own — a reader who missed the meeting can pick it up cold and know what to do next. Every action has an owner and a due date. "Let's discuss again" is not a decision.

Write the handoff doc for a vacation or OOO period. The reader is the person (or people) covering. Cover: what's running while you're out (with owner + status), the 3-5 decisions you are pre-delegating (who can decide what, up to what threshold), the things that should explicitly wait until you are back, your escalation phone tree (under what condition do they contact you on holiday, and how), and the inbox triage rule you have asked your team to follow.

Banned: "Reach out anytime if you have questions" — defeats the purpose. The escalation rule is specific: e.g., "text me only if production is down for paying customers >30 min or a layoff/legal issue lands in your lap." Decisions you delegate are time-bounded and budget-bounded (e.g., "up to $5k in approval, single-day call"). Things that wait must be safe to wait — if they're not, they're not a wait, they're a delegate. End with the "on return" expectation: what should I find in my inbox/Slack vs. what should be resolved.
No filler openings ("Certainly!", "Great question"). No closing pleasantries. No throat-clearing. Skip the preamble — start with the substance.

Output:
# OOO: <name> — <start date> to <end date>
## Coverage at a glance
| Stream | Owner while I'm out | Status |
|---|---|---|
## Decisions I have pre-delegated
- <decision class> → <person>, up to <threshold>
- ...
## Decisions that wait until I'm back
- <thing> — safe to wait because <reason>
## When to contact me on vacation
- Only if: <specific conditions>
- How: <single channel — text to <name>, not Slack>
- Who decides if it meets the bar: <name>
## Inbox / Slack while I'm out
- The rule the team should apply: <e.g., "reply if you can answer; otherwise let it sit">
## What I will find on return
- Resolved: ...
- Awaiting my decision: ...
## First-day-back plan
- 9-11: read the awaiting-decision queue
- 11-12: walk the room (catch up with each covering person 10 min)
- afternoon: re-engage with the priority project

OOO dates: {dates}
My role + what I usually decide: {role}
Active projects I lead or block: {projects}
Known decisions coming up during OOO: {pending_decisions}
People who can cover: {coverage}
Real-emergency definition for my job: {emergency}