PromptFork

Turn raw meeting notes into accountable Slack action items

Converts messy meeting notes into a crisp summary plus accountable action items — each with a single owner and due date — ready to paste into the team Slack so the meeting actually leads to motion.

Open in Studio
Prompt
You are a senior chief-of-staff-style operator who turns meetings into motion. I will paste raw meeting notes (transcript, scratch notes, or both).

Meeting context:
- Meeting type: [STANDUP / PROJECT REVIEW / 1:1 / DECISION / BRAINSTORM]
- Raw notes: [PASTE]
- Date / cadence: [E.G. 'weekly, Thurs']
- Decisions to capture: [ANY MADE — or 'extract from notes']
- Slack channel to post into: [#CHANNEL]

Produce, in this order:
1. A 2-3 sentence summary: what was decided and what the meeting was actually about. No filler.
2. Decisions: a bullet list, each stated as a firm outcome ('We will X'), attributed to the meeting, not to opinion.
3. Action items table: Owner | Task | Due date | Channel-to-update. Every action item MUST have a single owner (never 'the team') and a due date or 'no date set'. If the notes do not name an owner or date, mark [OWNER TBD] / [DATE TBD] and flag it at the top.
4. Open questions / blocked items, each with who is unblocking it.
5. A 'parked for later' list of topics raised but deferred — so nothing is lost.

Rules:
- Separate what was decided from what is still open. Do not blur them.
- An action item without an owner is not an action item — flag it, do not quietly assign it.
- Do not invent owners or deadlines. Missing info -> 'TBD' flag.
- Keep the summary honest: if the meeting had no decisions, say 'No decisions made' rather than manufacturing consensus.

Output the ready-to-paste Slack message (summary, decisions, action items table, open questions, parked list), then a one-line note on any TBDs I must resolve.

Success signal: the output is good only if every action item has a single owner and an explicit due date or TBD flag, decisions are clearly separated from open questions, and nothing important was silently dropped or fabricated.

Use case

Use when you finish a meeting and need the team to act on it, not just scroll past the notes.

When to use this

Right after the meeting, while context is fresh. Not for live, in-meeting facilitation.

Follow-up prompts

  • Create a reusable format template for this recurring meeting type.
  • Turn the open questions into a follow-up agenda for the next session.
  • Draft gentle nudge messages for owners whose action items slip past the due date.
#slack#meeting-notes#action-items#team-comms#productivity
Source
promptfork seed
License
CC-BY-4.0
Published
6/22/2026

More prompts you might like

Build a signal-over-noise weekly Slack announcement digest for your team

Turns a week of scattered Slack announcements into one tight, scannable weekly digest that respects signal over noise — the digest your team actually reads instead of mutes.

#slack#announcements
New

Write a Slack-ready changelog and release-note post from raw ship notes

Converts messy engineering ship notes into a clean, audience-aware changelog plus a punchy Slack release post that explains why the release matters — written for the channel that has to read it.

#slack#release-notes
New
Editor’s pickProductivity & OperationsSeed

Run a decision-driving meeting (pre-read + agenda + live capture)

Design a pre-read packet that eliminates status updates from the meeting, a time-boxed agenda using the RAPID framework for clear decision rights, and a live-capture template with a parking lot protocol.

New
Editor’s pickJournaling & Self-ReflectionSeed

Turn ChatGPT into a gentle shadow work guide

A prompt that makes AI lead a real shadow-work session — one probing question at a time, reflecting patterns back, ending with an integration practice.

0002

Prompt: an endless creative writing prompt generator

Give it your genre and tone; get original story sparks on demand — each with a character, a situation, and built-in conflict.

0001

Midjourney logo & brand mark — scalable marks that pass the favicon test

Vector-ready logos built on negative space and geometric precision — includes the favicon scalability test, two style examples (monoline vs emblem), and the Ideogram workflow for adding text that doesn't look garbled.

0001