Prompt library · AI · 12 prompts
Prompts from the guide
From a meeting recording to notes with tasks in a minute
12 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.
The agenda as the skeleton of the future notes
Build a meeting agenda so it can easily turn into notes afterward. Meeting: [name], length [60] minutes, participants and roles: [name — role, name — role, …] Topics on my list: [bulleted list] Carried over from last time: [unfinished items] For each agenda item, give: - item name and time limit in minutes - item type: DECISION / INFORMATION / DISCUSSION (no decision) - what specifically should be known or decided by the end of it - who introduces the item Order the items so the decision items come in the first half. At the end, add a block called “What we won't get to today” and leave it empty. The total time must not exceed the meeting length; leave a 5-minute buffer.
What to do to the transcript before sending it on
Here's a raw meeting transcript. Don't summarize it and don't drop any content — just clean it up into a readable form: - remove filler words and false starts (“like,” “um,” “you know”) - merge repeated sentences and stumbles into one smooth sentence - keep the speaker breakdown and the exact wording anywhere a commitment, number, deadline, or name was said - mark passages that clearly don't belong to the meeting (technical issues, private tangents) with a line reading [OFF TOPIC] and drop the text - where the audio is clearly mis-heard or doesn't make sense, write [UNINTELLIGIBLE] instead of guessing Don't add anything or guess what the speaker meant to say. Transcript: [paste transcript]
When you can't record
Here are my raw meeting notes — written in a rush, incomplete sentences, abbreviations. Meeting: [name], date [date], participants: [names and roles]. Turn them into structured notes using the same format I use for transcripts: decisions / tasks with who-what-deadline / open items. Key rule: work only with what's in the notes. Where a note is ambiguous (unclear who got a task, or whether it was actually a decision), don't guess — put the item in a section called “TO FILL IN” with the question I need to answer. Notes: [paste notes]
The main prompt for turning a transcript into notes
You are a meeting note-taker. Create notes from the attached transcript. Work strictly from the transcript — don't add anything from general knowledge and don't guess what speakers might have meant. Meeting context: Name: [name]. Date: [date]. Length: [60] minutes. Participants and roles: [name — role, …] Agenda: [agenda items] Output in four separate sections, in this order: 1. DECISIONS Only things that were actually closed. For each: - the decision stated in one declarative sentence - who decided (name) and who explicitly agreed - what options were weighed and why this one won If a decision wasn't clearly made, DON'T put it here — it belongs in section 3. 2. TASKS A table: task | owner (one name) | deadline | where it came from - phrase the task as an action with a verb, not a topic - the owner is always one specific person, never “the team” - where no deadline was said, write “NO DEADLINE STATED,” don't invent one - where it's unclear who took the task, write “OWNER UNCLEAR” 3. OPEN ITEMS What was discussed without reaching a conclusion. For each: what was being worked through, what the options are, what's blocking a decision, who needs to close it out and by when it has to be decided. 4. FOR THE RECORD Information without action items (numbers, statuses, announcements), as brief bullet points. Formatting requirements: - no introduction, no summary at the end, go straight into the sections - for each item, note in parentheses which speaker's words it's based on - if something is missing or unintelligible in the transcript, say so instead of guessing Transcript: [paste transcript]
Tasks in a who-what-by-when format
From these notes (or this transcript), pull out ONLY the tasks and rewrite them in a single format I can work with directly. One line per task: [owner] — [action starting with a verb] — by [date as MM/DD] Rules: - one task = one action = one owner; split up compound tasks - convert relative deadlines to actual dates; today is [date], “by end of week” = [Friday's date], “next week” = [date] - when no deadline was stated at all, write “by ??” and add a note on the line saying I should ask about it - leave out anything that was just an idea, a suggestion, or a conditional statement (“if we had time, we could…”) — list those separately under a heading called UNCOMMITTED IDEAS - sort by deadline, soonest first At the end, write a total: how many tasks each person has.
How to recognize a decision in spoken language
Go through this meeting transcript and audit the decisions. I only care about what was actually closed. List a table with columns: topic | what was proposed | status | evidence from the transcript | what's missing to close it out Fill in status with one of: - DECIDED — a clear conclusion was reached and nobody objected - APPARENTLY DECIDED — something sounding like a conclusion was said, but agreement from others is missing or it was immediately questioned - NOT DECIDED — it was discussed, no conclusion was reached In the “evidence from the transcript” column, quote the exact sentence (and who said it) the status is based on. Don't state a status without a quote. For APPARENTLY DECIDED items, write exactly who needs to confirm what for it to become a real decision. Transcript: [paste transcript]
When a decision gets reversed halfway through the meeting
Look through this transcript for contradictions and changes of mind over the course of the meeting. List: 1. Things that were agreed early on and later questioned or changed — for each, both passages and who said them. 2. Statements by two people that directly contradict each other (for example, different numbers, different deadlines, different descriptions of a status). 3. Tasks that got reassigned to a different person during the meeting. For each item, note which version is later according to the transcript, and phrase a question I can send to participants to confirm. Don't decide for me which version stands.
A prompt for disputed items and loose ends
Read this meeting transcript like someone looking for holes. I don't care what went well. I care what stayed open. Return five lists: 1. UNANSWERED QUESTIONS Questions someone asked that never got a reply. For each: who asked, about what, and why it fell through the cracks (ran out of time / got answered with something else / nobody knew). 2. TASKS WITHOUT AN OWNER Things someone said would happen, but nobody actually took on. Quote the sentence you're basing this on. 3. TASKS WITHOUT A DEADLINE Who took on what, but without a date. For each, suggest a deadline that would make sense and why — as a suggestion to confirm, not a fact. 4. UNSPOKEN DISAGREEMENTS Places where someone expressed doubt or a reservation and the discussion moved on anyway. Quote the exact sentence and who said it. 5. DEPENDENCIES AND RISKS Things we can't do until something else happens (or until someone outside this meeting delivers something). For each item, note who I should ask to close it out. When a category has nothing in it, write “none” — don't invent items. Transcript: [paste transcript]
A “nobody picked this up” section in the notes themselves
Add a separate section to the notes called “No owner.” Include things that were discussed in the meeting, would make sense to do, but nobody took on. Maximum 5 items, sorted by how quickly they'll turn into a problem. For each, one line: what it is — who would logically take it on (a suggestion, not an assignment) — what happens if nobody does. Write it plainly and without blame. The goal isn't to call anyone out — it's to give people a chance to step up before it starts to burn.
What a human has to check
Check this draft of the notes against the meeting transcript and list what you find. Don't fix anything, just show me where to look. Return four lists: 1. Statements in the notes that have no support in the transcript (added or guessed) — quote the notes for each one. 2. Names you're not confident you attributed correctly (similar-sounding names, speakers switching) — with the passage from the transcript. 3. Numbers, dates, and amounts in the notes next to their wording in the transcript, so I can compare them. 4. Phrasing that was hedged in the transcript (“maybe,” “probably,” “I think”) and shows up in the notes as a firm commitment. Notes: [paste notes] Transcript: [paste transcript]
When and who to send the notes to
Turn these meeting notes into three versions for different audiences. 1. FOR PARTICIPANTS — full notes unchanged, just add 3 bullet points at the top: “what changed since last time.” 2. FOR LEADERSHIP — maximum 6 sentences: what was decided, what impact it has on timeline and budget, what we need from them. No discussion details, no names except the ones that have to be mentioned. 3. FOR EACH TASK OWNER — a short personalized block: “Hi [name], from today's meeting you have:” followed by their tasks with deadlines and one sentence of context for why. Separately, list what they're waiting on and what others are waiting on from them. Write in plain, matter-of-fact English, no extra pleasantries. Don't add anything that isn't in the notes.
Phase 7: follow-through and a series of meetings
Here are the notes from the last meeting and my notes on what's happened since then. Notes from [date]: [paste notes] What I know about the status: [paste notes, email replies, task status] Prepare an opening block for today's meeting: 1. Tasks from last time: done / in progress / not started — for the not-started ones, the owner's name and original deadline 2. Decisions from last time that have since turned out to be in dispute 3. Open items from last time that need to be closed out today, sorted by urgency 4. Three questions to open the meeting with, so everyone knows right away where things stand Where I don't have status information, write “status unknown” and add it to the list of things I should ask about.