Skip to content
MISSIONBuilding to $50K/year · partnership threshold — every $20 subscription reserves 10 meals in the fund. Report published monthly.SEE THE PROGRESS →
PROMPT · WORK

Turn a messy Slack thread into a one-pager.

The move from '90 messages across three days' to 'here's a document you can share with the room that wasn't in the thread'.

Run in LADLE →
USE CASE

A decision brewed in a Slack thread with 12 participants across four days. Someone senior asks 'what did we land on'. Skimming the thread is a 20-minute job. This prompt condenses the thread into the one-pager you'd have written if the discussion had happened in a doc from the start.

THE PROMPT
You are converting a messy multi-day Slack thread into a shareable one-pager. I'll paste the thread below. Return exactly these sections in Markdown, in this order:

**Context** — one paragraph, four sentences max. What triggered the discussion, and what's at stake.

**Options considered** — bulleted list of every distinct proposal from the thread. One line each. Attribute to the person who raised it in brackets.

**Where we landed** — one paragraph. State the current best-supported direction, whether it was formally decided or is the emerging consensus.

**Open tradeoffs** — bulleted list of the tradeoffs that were named but not resolved. These are the things a new reader would ask about.

**Next step** — one line. The specific next action and the person who owns it. If the thread didn't produce one, write "Not yet named — needs an owner."

Voice: neutral, third-person, factual. Do not editorialize. Do not omit the option that lost — the fact that it was considered is part of what a reader needs to know.

Here is the thread:

[PASTE THREAD HERE]
EXAMPLE OUTPUT
**Context** The 8/3 outage exposed a gap in our on-call rotation — no one was paged for the first 40 minutes because the alert routed to a channel no active engineer was watching. The team's been debating the fix for four days. **Options considered** - Move on-call alerts to PagerDuty with a paid tier [Sam] - Fix the routing on our existing Slack integration [Jamie] - Rotate a dedicated "alerts channel" watcher weekly [Priya] - Do nothing until we have a second engineer to actually rotate with [Rae] **Where we landed** Sam's PagerDuty proposal is the direction — the fix isn't the routing rule, it's the fact that Slack isn't a paging medium. Cost is manageable at team-of-3 pricing. **Open tradeoffs** - $29/user/mo × 3 = $87/mo new spend not previously budgeted. - PagerDuty's phone-call escalation is aggressive; we haven't decided the exact policy for after-hours. **Next step** Sam sets up the PagerDuty trial and drafts the escalation policy for team review by Aug 15.
RELATED · WORK
← All Work promptsStart with LADLE
0meals fundedROLLING TOTAL · UPDATED HOURLY
SEE THE RECEIPTS →