Issue 36 · 10 Oct 2026 · Easy · Free
Meeting Notes to Tasks
The meeting ended. The doc is a pile of half sentences, and on Thursday nobody remembers who said they would email the vendor.
Turn a messy transcript into decisions, owners, due dates, and a Slack note people will actually read.
- Category
- Productivity
- Runs in
- ChatGPT
- Claude
- Gemini
What you put in and what you get out
You put in
Paste the mess, plus the date. A transcript, your own bullets, or a voice-memo dump all work. Put the meeting date and the names in the room at the top if you have them. Relative dates like 'Thursday' need that anchor.
Agent
Meeting Notes to Tasks
You get out
The Slack note. Five lines, no dentist, no 'maybe.' Finance is an open question with Ari as the likely sender, marked as an assumption.
Sample you can paste
Meeting: launch check, 14 Oct 2026. People: Ari (PM), Noor (eng), Sam (support). Notes: - Ari wants the pricing page live before Friday. Noor said the toggle is behind a flag, can flip Thursday if copy is final. - Sam: three tickets this week about the receipt email going to spam. maybe we should look? not sure who. - decided NOT to discount annual this month. - someone should tell finance. Ari? - next tuesday sync, same time. - Noor mentioned their dentist Friday morning so don't book them then. skip that in the public note.
Share this agent
Meeting Notes to Tasks — You put in Meeting: launch check, 14 Oct 2026. People: Ari (PM), Noor (eng), Sam (support).. You get out The Slack note. Free from One Agent a Day.
30-second demo
0:00
The notes, as typed
Pricing page before Friday. Flag flips Thursday if copy is final. Receipts hitting spam. No annual discount. Tell finance. Noor's dentist stays out of the public note.
How it works
Meetings produce a feeling that something was decided. The notes produce a paragraph. This agent splits the paragraph into decisions, tasks, open questions, and a short note you can post.
It will not invent an owner. If the notes say "someone should tell finance," the task is unassigned and the question stays open. It also keeps personal asides out of the shared summary. A dentist appointment is not a status update.
Anchor the dates
"Thursday" means nothing without the meeting date. Put Meeting date: 2026-10-14 on the first line. The agent then writes real dates and labels anything it inferred.
Works on a raw transcript. You do not need to clean it up. Cleaning it up is the job.
Use it
Step 1
Paste the mess, plus the date
A transcript, your own bullets, or a voice-memo dump all work. Put the meeting date and the names in the room at the top if you have them. Relative dates like 'Thursday' need that anchor.
Step 2
Name the audience of the summary
Say where the short version will be posted: Slack, email, or the ticket tracker. The agent writes that version without the side comments that should stay in the room.
Step 3
Paste the prompt, then the notes
New chat. Paste the prompt first so the notes cannot override it. If a name owns a task, it has to appear in the notes or the agent marks the owner as unassigned.
Step 4
Copy tasks out, then send the summary
The task list is the system of record. The Slack block is what you paste. Do not send the parking lot unless you mean to.
Prompt
meeting-notes-to-tasks.prompt.txt
You convert meeting notes or a transcript into a record people can act on. You are literal. You separate what was decided from what was merely said.
INPUT
- Meeting date, if known. If missing, keep due dates relative and mark them "date not anchored."
- Participant names and roles, if known.
- The notes or transcript.
- Where the short summary will be posted: Slack, email, or a ticket. If they did not say, write the summary for Slack.
RULES
- A decision requires agreement, not a suggestion. "Maybe we should" is not a decision.
- A task needs an owner. If the notes do not name one, owner is "unassigned." Never invent a person.
- A due date must come from the notes or from the meeting date plus a phrase like "by Friday." Show the phrase you used.
- Leave personal logistics (health, family, commute) out of the shared summary. You may omit them entirely.
- Do not add tasks that nobody mentioned.
- Mark assumptions in their own section. Do not bury them in a task title.
- Quotes from the notes are fine when a decision is easy to misread. Do not quote filler.
OUTPUT
## Decisions
Bullets. If none, write "None captured."
## Tasks
One task per line: owner, action, due date, definition of done.
Unassigned tasks are allowed and must say "unassigned."
## Open questions
Bullets. Include who might know, if the notes imply it, and mark that as an assumption.
## Parking lot
Topics raised and explicitly not decided.
## Post this
The short summary, under 120 words, safe to paste in the channel they named.
## Assumptions
Bullets, or "None."Related agents
Tomorrow's drop
Get the next agent in your inbox
One email when the drop goes up. No digest, no course. Unsubscribe whenever the provider lets you.
Pro and custom
€9/month when Pro opens
Early look at the next drop, a better archive, and the occasional agent that does not fit the public mix. The daily agent stays free. A custom build is €49–199. Nothing is charged from this form.
Join the Pro waitlist