{"version":"1.1.0","schema":"https://oneagentaday.com/api/schema.json","agent":{"title":"Meeting Notes to Tasks","slug":"meeting-notes-to-tasks","date":"2026-10-10","issue":36,"category":"productivity","categoryLabel":"Productivity","tags":["meetings","tasks","notes"],"difficulty":"easy","runtimes":["ChatGPT","Claude","Gemini"],"excerpt":"Turn a messy transcript into decisions, owners, due dates, and a Slack note people will actually read.","problem":"The meeting ended. The doc is a pile of half sentences, and on Thursday nobody remembers who said they would email the vendor.","videoUrl":null,"url":"https://oneagentaday.com/agents/meeting-notes-to-tasks","apiUrl":"https://oneagentaday.com/api/agents/meeting-notes-to-tasks.json","promptUrl":"https://oneagentaday.com/agents/meeting-notes-to-tasks/prompt.txt","configUrl":null,"configFilename":null,"license":"CC-BY-4.0","howItWorks":"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.\n\nIt 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.\n\n## Anchor the dates\n\n\"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.\n\nWorks on a raw transcript. You do not need to clean it up. Cleaning it up is the job.","steps":[{"name":"Paste the mess, plus the date","text":"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."},{"name":"Name the audience of the summary","text":"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."},{"name":"Paste the prompt, then the notes","text":"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."},{"name":"Copy tasks out, then send the summary","text":"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."}],"demo":[{"second":0,"label":"The notes, as typed","detail":"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."},{"second":8,"label":"Decisions","detail":"No annual discount this month. Pricing page is the launch gate. Thursday is the flag day only if copy is locked."},{"second":16,"label":"Tasks with owners","detail":"Ari: final pricing copy, due Wed 15 Oct. Noor: flip the flag Thursday, blocked on that copy. Sam: open a spam-folder ticket and assign an owner, because the notes never named one."},{"second":24,"label":"The Slack note","detail":"Five lines, no dentist, no 'maybe.' Finance is an open question with Ari as the likely sender, marked as an assumption."}],"sampleInput":"Meeting: launch check, 14 Oct 2026. People: Ari (PM), Noor (eng), Sam (support).\nNotes:\n- Ari wants the pricing page live before Friday. Noor said the toggle is behind a flag, can flip Thursday if copy is final.\n- Sam: three tickets this week about the receipt email going to spam. maybe we should look? not sure who.\n- decided NOT to discount annual this month.\n- someone should tell finance. Ari?\n- next tuesday sync, same time.\n- Noor mentioned their dentist Friday morning so don't book them then. skip that in the public note.\n","prompt":"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.\n\nINPUT\n- Meeting date, if known. If missing, keep due dates relative and mark them \"date not anchored.\"\n- Participant names and roles, if known.\n- The notes or transcript.\n- Where the short summary will be posted: Slack, email, or a ticket. If they did not say, write the summary for Slack.\n\nRULES\n- A decision requires agreement, not a suggestion. \"Maybe we should\" is not a decision.\n- A task needs an owner. If the notes do not name one, owner is \"unassigned.\" Never invent a person.\n- A due date must come from the notes or from the meeting date plus a phrase like \"by Friday.\" Show the phrase you used.\n- Leave personal logistics (health, family, commute) out of the shared summary. You may omit them entirely.\n- Do not add tasks that nobody mentioned.\n- Mark assumptions in their own section. Do not bury them in a task title.\n- Quotes from the notes are fine when a decision is easy to misread. Do not quote filler.\n\nOUTPUT\n## Decisions\nBullets. If none, write \"None captured.\"\n\n## Tasks\nOne task per line: owner, action, due date, definition of done.\nUnassigned tasks are allowed and must say \"unassigned.\"\n\n## Open questions\nBullets. Include who might know, if the notes imply it, and mark that as an assumption.\n\n## Parking lot\nTopics raised and explicitly not decided.\n\n## Post this\nThe short summary, under 120 words, safe to paste in the channel they named.\n\n## Assumptions\nBullets, or \"None.\"","config":null}}