How to Turn a Slack Thread into a Meeting Agenda

Anyone drowning in a 40-message channel can turn a Slack thread into a meeting agenda in 15 minutes: extract decisions already made, list open asks, name owners, and time-box three items. Run it in ChatGPT, Claude, or Gemini before you book an hour that will replay the thread out loud.

A thread is a pile, not a meeting. Force a shape the room can use without scrolling. Status stays a message. The meeting is for a decision, a blocker, or a date someone must own.

If you still paste "summarize this Slack" into a blank chat, read what a skill prompt actually is and save the card at the end.

Turn a Slack thread into a meeting agenda in five steps

1. Export raw, then redact

Copy the thread in order. Before you paste into ChatGPT, Claude, or Gemini, strip secrets you would not put in a vendor tool.

Instruct: "Do not summarize yet. List messages as bullets: who, time if present, and the claim in their words. Mark questions as ASK. Mark anything that sounds decided as DECISION. Mark anything with no owner as UNOWNED."

The model will try to write minutes. Minutes are a lie before the meeting. Hold it to a ledger.

2. Split decided from open

Send the ledger back. Instruct: "Two lists only. List A: decisions already made, with the message that proves them. List B: open asks. If a decision has no proof, move it to List B. Do not invent consensus."

Consensus is the word models use when three people reacted with an emoji. An emoji is not a decision.

If the dump is a mess of half-thoughts, use the same raw-then-shape discipline as turning a messy note into a one-page brief. Do not ask for an agenda in the first prompt.

3. Force a three-item agenda

Now ask for the page. Hard cap: three talking items, plus a pre-read.

• Item — the decision or blocker, in a verb-plus-object sentence.
• Owner — one name from the thread, or UNKNOWN.
• Time box — 8 or 12 minutes. Not "discussion."
• Pre-read — links that must be opened before the call, not during it.

Tell the model: "If List B has more than three asks, rank by whether a date slips this week. Keep three. Park the rest as parking lot, one line each, no debate text. Do not add an icebreaker, a round of updates, or AOB theater."

AOB is how 25 minutes becomes the thread again.

4. Name who must be in the room

Instruct: "List required people: each item owner plus the one person who can decide. Everyone else is optional. If a name never appears in the thread, do not invite them."

ChatGPT will add "stakeholders." Claude will add a note about alignment. Gemini will add speed and a fourth item. Cut all three habits.

You pick the room. The model proposes. Park the loop in the Promptcrates library of reusable prompts. The agenda instance is disposable.

5. One human pass, then send the invite

Read the three items out loud. If you cannot say why a person must speak, they are optional.

Check three traps:

• An item that is actually a status update.
• An owner who is a team name.
• A time box that sums to more than 25 minutes.

Fix those in your own words. Send the agenda in Slack before the calendar invite. Then stop. Do not add a fourth item "if we have time."

Reusable skill card

Trigger: A Slack thread has outgrown another message, and someone is about to book a meeting.

Input: The redacted thread in order, plus a hard cap of three items and a 25-minute default.

Output: A ledger of DECISION / ASK / UNOWNED, then an agenda: three verb-plus-object items, one owner each, time boxes, a pre-read list, a parking lot, and a required-versus-optional invite list.

Stop: After one human read-aloud pass. No AOB. No status block. No fourth item. No invented consensus.

Takeaways

• Ledger first. Decisions and asks second. Agenda third. Never in one prompt.
• Three items. Twenty-five minutes. Status stays in Slack.
• An emoji is not a decision. UNKNOWN is better than a fake owner.
• Invite owners and one decider. Cancel if List B is empty.