đ Works best with your call recorder. Connect Fathom, Fireflies, or Zoom and Jeremy AI pulls the meeting notes for you, no pasting.
Paste your raw meeting notes. Get one file back: an owner-tagged task table, a decisions list, an open questions list, a short recap draft, a not-provided list and a check table. Nothing is sent.
You'll see the SAMPLE meeting notes pasted in with the rules, the task list built in about 4 seconds on screen (the real wait was about 49 seconds), the file saved with nothing sent, the task table, the recap draft and not-provided list, and the check table.
What this use case does and who it's for
The meeting ends. Everyone nods. A week later nobody remembers who was doing what. The notes are a messy list, and turning them into clear tasks is a job nobody wants.
Here's the shortcut. Paste the notes. Jeremy AI sorts them into tasks, decisions and open questions. It tags every task with an owner and a due date, but only if your notes said so. If they didn't, it says "not provided" and flags the gap. Six parts:
A task table. Four columns: task, owner, due and status. One row per task, in the order the notes listed them.
A decisions list. Only the decisions the notes stated.
An open questions list. Only the questions the notes stated.
A recap message draft. 80 words or fewer. It lists the clear tasks and asks owners to confirm. It's signed with a placeholder on its own last line.
A not-provided list. Everything the file would need that the notes didn't say, like the meeting date or the attendee list.
A check table. Three columns: item, source and status. It shows each task, decision and question was captured.
It's for team leads, agency owners, coaches with a team and anyone who runs a weekly meeting. It's drafts only. Jeremy AI doesn't send anything.
What you need before you start
A Jeremy AI account. Nothing to connect to try the sample.
Your meeting notes. The sample is made up: SAMPLE Harbor Team, a small marketing team, with eight lines: two decisions, five tasks and one open question.
Your status rules. The sample sets four: "clear" when an owner and a due date are both stated, "needs owner," "needs due date" and "needs both."
Honest gaps. The sample says meeting date, attendee list, sender name and links are "not provided."
The rules. The sample uses HARD RULES: copy owners, task wording and due dates exactly as stated, never assign an owner, invent a due date or infer a detail not stated, never calculate a number or date, no praise or opinions, and never address you by name.
How to set it up
You use the default Jeremy AI worker. There's nothing to build.
Open Jeremy AI. From the dashboard, type in the main box. Check the worker selector says Jeremy AI.
Paste the prompt below. Swap your own meeting notes in where the sample notes are.
Click Send message.
Wait. The walkthrough speeds this part up. In real time it took about 50 seconds.
When it says the file is saved, read the chat summary first.
Open the file card and read the task table.
Scroll to the decisions, the open question, the recap draft, the not-provided list and the check table.
The prompt
This is the exact prompt from the walkthrough. The team, the names and every date are SAMPLE and made up. Replace them with yours.
Act as my "Meeting Notes to Tasks" worker for SAMPLE Harbor Team, a small marketing team (all data below is made up). Turn the SAMPLE meeting notes below into an owner-tagged task list. Create ONE file named meeting-notes-task-list.md using the file tool (reply with a short summary only) with: 1) a TASK TABLE with exactly 4 columns (task, owner, due, status), one row per task in the order listed in the notes, 2) a DECISIONS list with only the decisions stated, 3) an OPEN QUESTIONS list with only the questions stated, 4) a RECAP MESSAGE DRAFT of 80 words or fewer that lists the clear tasks and asks owners to confirm, signed with the placeholder "[sender name: not provided]" on its own last line, 5) a NOT PROVIDED list, 6) a CHECK table with exactly 3 columns (item, source, status). STATUS RULES: clear = owner and due both stated, needs owner = owner not stated, needs due date = due not stated, needs both = neither stated. In the table write "not provided" for any missing owner or due date. HARD RULES: copy owners, task wording and due dates exactly as stated, never assign an owner, invent a due date or infer a detail not stated; never calculate a number or date; write "not provided"; no praise or opinions; every table has 4 columns or fewer and cells of 12 words or fewer; never address me by name anywhere in the chat reply or the file. Drafts only, nothing is sent.
MEETING NOTES (SAMPLE):
- Decided: move the Monday call to 10am.
- Ad creative refresh: Priya to send 3 new hooks by Friday.
- Update the booking page headline: Marcus, due next Tuesday.
- Review last week's support tickets: nobody assigned, due not stated.
- Send the webinar replay email: Elena, due not stated.
- Clean up the CRM tags: owner not stated, due Thursday.
- Decided: keep the 2 best ads running.
- Open question: who owns the monthly report?
Not provided: meeting date, attendee list, sender name, links.
Prompting tips and how to adapt it
Define each status. The prompt says clear means owner and due both stated, and spells out the other three. Jeremy AI applies them. It doesn't guess.
Say "not provided" out loud. Tell it to write "not provided" for a missing owner or due date. It won't fill the gap with a guess.
Copy, don't reword. The prompt says to copy owners, task wording and due dates exactly. "Next Tuesday" stays "next Tuesday." It doesn't turn it into a date.
Keep the order. The prompt says one row per task, in the order listed in the notes. That makes the table easy to check against your notes.
Cap the recap. The recap is 80 words or fewer and ends with "[sender name: not provided]" on its own line. You fill in your name before you send.
Ban new numbers and dates. The prompt says never calculate a number or date.
Ban opinions. The prompt says no praise or opinions. It's a task list, not a pep talk.
Adapt it. Swap in any meeting: a weekly team call, a client kickoff or a coaching group. Add a column or a status if you need one, and keep tables at 4 columns or fewer.
The result to expect
One Markdown file named meeting-notes-task-list.md, titled "Meeting Notes to Tasks (SAMPLE Harbor Team)." With the sample data you should see:
A 4-column task table with five rows, in the order of the notes.
Ad creative refresh: send 3 new hooks. Priya, Friday, clear.
Update the booking page headline. Marcus, next Tuesday, clear.
Review last week's support tickets. Owner not provided, due not provided, needs both.
Send the webinar replay email. Elena, due not provided, needs due date.
Clean up the CRM tags. Owner not provided, Thursday, needs owner.
A decisions list with two items. Move the Monday call to 10am. Keep the 2 best ads running.
An open questions list with one item. Who owns the monthly report?
A recap message draft. It names the tasks that are clear, says the ticket review needs an owner and a due date, flags the missing owner on the CRM tags and the missing due date on the webinar email, and asks owners to confirm. It ends with "[sender name: not provided]" on its own line.
A not-provided list. Four items: meeting date, attendee list, sender name and links.
A 3-column check table. Eight rows, one for each task, decision and question. Each one has the source "Meeting notes" and the status "captured."
The chat reply summarizes the file and says nothing was sent.
These are sample results from made-up notes. Wording changes from run to run. Read every line before you send anything.
Common mistakes and fixes
An owner appears that your notes never gave. Delete it. Remind it: "Never assign an owner."
A due date appears that you never gave. Delete it. Remind it: "Never invent a due date. Write not provided."
"Next Tuesday" turns into a calendar date. Fix it. Remind it: "Copy due dates exactly as stated. Never calculate a date."
A status doesn't match your rules. Fix it by hand and say: "Apply the status rules exactly."
A decision or question is added that wasn't in the notes. Delete it. Remind it: "Only list decisions and questions that were stated."
The recap runs long. Remind it: "The recap is 80 words or fewer."
The recap makes a promise for someone. Rewrite it. The recap should only list the tasks and ask owners to confirm.
You send the recap with the placeholder still in it. Don't. Fill in your name first.
You send it as is. Don't. Check the table against your notes once, then send the recap yourself.