Meeting Recording to Minutes & Actions
Turn a meeting recording into structured minutes plus a clear action-item list — who agreed to do what by when — derived from the audio. Transcribes the recording FIRST (with speaker labels so attribution is possible), then summarizes into decisions, discussion, and assigned action items with owners and due dates. The transcribe-then-summarize ordering is essential: you cannot reliably attribute decisions and owners without first knowing who said what, and minutes without owners are useless.
Steps
Entry step: transcribe. Each step names the specialist role it wants; the full working prompt is expandable.
- Transcribe the meetingdeveloperentry
STT with speaker labels + timestamps
Show working prompt
Get an attributable transcript BEFORE summarizing. Step 1: record the source (path, duration, and attendee names if known). Step 2: run speech-to-text over the WHOLE recording with diarization, labeling speakers (map to real names where you can infer them from introductions). Step 3: timestamp utterances so decisions/actions can cite a moment. Step 4: lightly clean filler for readability but keep commitments verbatim. Step 5: write the labeled transcript to `notes/transcript.md` via write_task_note AND the produces path, and note its final timestamp vs the duration so coverage is checkable. On a loop-back, fix only flagged attribution/coverage gaps.
- Summarize into minutes & actionscopywriter
decisions, discussion, action items with owners + dates
Show working prompt
Write the minutes from the transcript. Step 1: lead with meeting metadata (title, date if known, attendees). Step 2: write a 'Decisions' section — each decision a tight bullet, with who made/agreed it. Step 3: write a 'Discussion' section summarizing key points by topic (not a re-transcription). Step 4: write an 'Action Items' section as a checklist where EVERY item has an explicit owner and a due date (write 'owner: TBD' / 'due: TBD' only if truly unstated — never silently drop the field). Step 5: add an 'Open Questions' section for anything unresolved. Do not invent commitments not in the transcript; attribute owners only when the transcript supports it. Write it all to `minutes.md` with clear headers. write_task_note the path and the action-item count. On a loop-back, fix only the flagged sections.
- Evaluatereviewer
Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
Show working prompt
Check the minutes against the recording. Step 1: confirm `minutes.md` has Decisions, Discussion, Action Items, and Open Questions sections with metadata up top (PASS/FAIL). Step 2: confirm EVERY action item has an owner and a due-date field (explicit or TBD) — no item missing the fields. Step 3: spot-check 3 decisions/actions against the transcript — each is real and attributed correctly, nothing invented. Step 4: confirm the summary is condensed (not a re-transcription) yet covers the major topics. Step 5: confirm transcript coverage reached the end of the recording. Write PASS/FAIL per criterion. Then route — this is the whole point of the loop: - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`. - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "summarize" })` to loop back. The builder fixes exactly those gaps. Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in. - Finishdeveloper
All acceptance criteria met. Stamp a short summary and report DONE.
Show working prompt
Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.
Triggers
Phrases that suggest this craftbook to a crew.
- meeting minutes from recording
- summarize this meeting
- action items from a call
- turn a recording into notes
- who agreed to what
Source
View this craftbook on GitHub · MIT license