async-decision-memo

# Async Decision Memo Skill Remote teams keep reinventing this badly: someone posts a doc, twelve people leave drive-by comments over two weeks, nothing resolves, and the decision happens in a meeting anyway — now with resentment. The async decision is a *process with a deadline*, not a document with comments enabled. This skill runs the whole protocol. ## What This Skill Produces - The **decision memo** (structured for silent reading, with the recommendation up front) - The **process wrapper**: named roles, response windows, comment-resolution rules, escalation - The **kickoff message** that opens the window and the **closing note** that records the outcome ## Required Inputs Ask for (if not already provided): - **The decision** — what's being decided, the options, the recommendation and its reasoning (rough notes fine) - **The people**: who *decides* (one name), who must be *consulted* (their objection could change the answer), who is merely *informed* - **The clock**: when is this decision needed, and what does it block - **The stakes** — reversible or one-way-door? (Sets the window length and the bar for escalation) ## The Protocol 1. **Write the memo for a silent first read.** Structure: **the decision needed** (one sentence) · **the recommendation** (up front — burying it invites a treasure hunt) · **context in prose** (full sentences force complete thinking; bullets hide gaps) · **options considered with real trade-offs** (a strawman option list discredits the w...