Every meeting ends with someone saying 'I'll send notes.' Most of the time those notes never arrive, or arrive as a wall of bullet points nobody re-reads. This workflow makes it fast enough to actually do — 12 minutes end-to-end per meeting, including a Friday sweep to check what's landed. The output is a decision log people scan on Monday and a specific action-item table the meeting owner uses to nag people mid-week.
Paste raw notes → structured log
Goal: Convert scrappy typed notes into three clean sections: decisions, actions, open questions.
You are converting my raw meeting notes into a decision log. I'll paste the notes. Return exactly three sections in Markdown: **Decisions** (one bullet per decision, present tense, no invented caveats), **Action items** (formatted [Owner] — action, by [date]; use [OWNER?] or [DATE?] if unclear), **Open questions** (attach a person + resolution owner to each). No preamble, no 'let me know if…'. If a section is empty, write 'None.'
Handoff: Paste this into your team's meeting-notes doc or Notion. Do not edit — send it as generated.
Fill the unknowns
Goal: Turn [OWNER?] and [DATE?] into real names and dates before sending.
For the following action items with [OWNER?] or [DATE?] placeholders, propose likely owners and dates based on the meeting context I gave you above. Frame each as 'Proposed [Name] by [Date] — because [reason].' I'll confirm or override before sending.
Send the digest
Goal: One message to the meeting attendees + one message to each action-item owner (personalized).
Draft two messages: (1) a summary post to the meeting attendees with the decision log; (2) individual Slack DMs to each action-item owner naming their specific action + deadline + one-line context. Voice: warm but direct. No 'I just wanted to loop back on…'.
Friday follow-up sweep
Goal: Check what landed, chase what didn't, before the weekend.
For the action items from my meetings this week, list which ones have visible completion signals (PR merged, doc published, message sent) and which don't. For the ones without signals, draft one nudge DM per owner — light, specific, non-guilt-inducing.
Handoff: The Friday sweep IS the workflow's compounding value. Skipping it turns the workflow into 'send notes and hope', which is the pattern this replaces.
Repeatability, not cleverness.
What lives where when the workflow finishes.
Decision log → team Notion or doc. Action items → your tracking tool (Linear, Asana, whatever). Friday sweep → your own calendar block for 15 minutes at 3pm. Nudges go one-per-person via DM, never in a group channel (guilt-inducing publicly, respectful privately).
The same shape, different jobs.
- Async standup variation — same shape, but Step 1 pastes typed standup updates instead of meeting notes.
- Board-meeting version — Step 3 skipped (board members don't need Slack DMs); Step 4 becomes a personal note to yourself about which items to reference at next board.
- 1:1 log — Step 1 keeps decisions section but action items are yours-to-yours; Step 3 is a self-DM summary saved to a Project.
- Customer-call notes — replace 'decisions' with 'customer commitments made'; downstream steps identical.
Prompts: meeting notes to action items · brief a collaborator
Use cases: work · product managers
Try this workflow once. Then decide if it earns a recurring slot.
The value compounds after the third run, not the first.