Meeting Notes to Action Items

What it takes in

The inputs you provide on each run, validated before anything executes.

2 tasks, run in order.

Each task passes its result to the next. Here's what each does and what it produces.

1. 01
   Extract the substance. Read {{meetingNotes}} carefully and pull out everything that matters: every decision that was made, every action item with its owner and due date, every open question left unresolved, and the key discussion points. Use {{attendees}} to attribute owners by name where possible, and {{meetingPurpose}} to judge what counts as signal versus noise. Assign an owner to an action item only if the notes make it clear who owns it: otherwise mark the owner as UNASSIGNED. Include a due date only if one was actually stated. Never invent owners, dates, or decisions. Present readably with headings and bullets, never JSON.

   Expected output

   A readable extraction with no JSON and no code blocks, organized under four headings: Decisions Made (one bullet per decision, stated plainly), Action Items (one bullet per item with the task, the owner: or UNASSIGNED: and the due date if one was stated), Open Questions (unresolved items that need follow-up), and Key Discussion Points (the substantive threads of the conversation, 3 to 7 bullets).
2. 02
   Produce the outputs people can use. Working only from the extraction in Task 1, create three deliverables. First, a crisp meeting summary for people who missed it: what the meeting was about (using {{meetingPurpose}} if provided), what was decided, and what happens next, in under 150 words. Second, an action-item table with columns Action, Owner, Due Date, listing every action item from Task 1: keep UNASSIGNED owners visible so they get resolved. Third, a ready-to-send follow-up email addressed to {{attendees}} recapping the decisions and asks: a clear subject line, a short opener, the decisions, the action items with owners, and a closing line inviting corrections. Professional but warm tone. Do not add any decision or action that was not in Task 1. Present readably, never JSON.

   Expected output

   A readable deliverable with no JSON and no code blocks containing three sections: Meeting Summary (under 150 words, written for someone who missed the meeting), Action Items (a table with columns Action, Owner, Due Date: UNASSIGNED owners and missing due dates shown as-is), and Follow-Up Email (a Subject line plus a complete, ready-to-send body recapping decisions and asks, ending with an invitation to flag corrections).