Turn a meeting transcript into notes people actually use — a faithful summary, the action items pulled out and assigned, and a clean shareable format.
A raw transcript is technically a record and practically useless — nobody rereads forty minutes of dialogue to find the one decision that affects them. The value is in what gets extracted: what was decided, who owns what, and by when. Doing that by hand is the chore that quietly doesn't happen, so the decisions evaporate. This workflow makes it mechanical: summarize the discussion faithfully, pull the action items out as their own list with owners, and format the result so it's actually worth sending.
Each step uses an existing NewPrompt tool, pre-filled by a matching resource. Open the resource to read it, or jump straight into the tool with the inputs ready.
Summarize the discussion faithfully
Condense the transcript into what was actually discussed and decided, keeping attribution straight, so the summary reflects the meeting rather than the model's guess at it.
Pull out the action items
Extract the commitments as a separate list — task, owner, and any due date — because an action buried in a paragraph is an action nobody does.
Format notes worth sending
Lay the summary and actions into a consistent notes template so the output is scannable and the same shape every meeting.
A transcript becomes notes people read: a faithful summary, an action list with owners, and a clean format — so decisions and commitments survive the meeting instead of dissolving in the recording.
Three things: a faithful summary of what was discussed and decided, a separate action-item list with owners and any due dates, and both laid into a consistent, shareable notes template. You still read it before sending — the workflow structures the notes, it doesn't verify the meeting for you.
Yes. The workflow starts from text — a transcript, or a transcription of the recording. It structures and extracts from that; it can't sit in on the call for you.
Because actions buried in prose get missed. Pulling them into their own list with owners and dates is the difference between notes that inform and notes that drive follow-through.
A summary prompt only does step one — condense the discussion. This workflow adds two steps: extracting the action items into a separate list with owners and dates, then formatting the summary and actions into a consistent, shareable template. That extraction and formatting is what makes meeting notes usable.
Paste your transcript into your own AI tool, then run the three step prompts in order: summarize the discussion faithfully, pull out the action items with owners, and format everything into the notes template. NewPrompt supplies the prompts and step order; you run each one and review the result.
Reassign it yourself — the extraction step guesses owners from the transcript, and it can misread who committed to what or invent a due date. Always check every action item and its summary against the actual discussion before sending, since the workflow structures notes but doesn't guarantee attribution is correct.
Complete build journeys that include this workflow as a stage.
The full path to an AI meeting assistant — define the use case, turn transcripts into structured notes, extract decisions and action items, classify follow-ups, write a shareable summary, evaluate accuracy, then ready it for the team.
Generate documentation that matches the code instead of drifting from it — have AI explain what the code really does, write it up as structured docs, then validate the format holds.
Pull a single coherent view out of a stack of sources — package them together, summarize each faithfully, then have AI synthesize across them instead of one at a time.