Prompt library
Summarize a meeting transcript
Splitting decisions from open questions is the summary's real job; most meeting notes blur them, and work stalls in the blur. The no-interpolation and [UNCLEAR] rules keep the summary auditable against the transcript, which is what makes people trust it enough to skip meetings.
Last reviewed July 17, 2026
The prompt
Summarize the meeting transcript below for someone who skipped the meeting and has 90 seconds.
{{transcript}}
Sections:
1. Decisions made: each with who committed to it and any condition attached. A decision without an owner gets flagged "unowned".
2. Open questions: what was raised and explicitly not resolved.
3. Action items: task, owner, deadline if stated. Never infer a deadline that was not said.
4. Notable positions: where named people disagreed and what each actually said (paraphrase tightly, attribute correctly).
5. One-line meeting verdict: what this meeting changed.
Rules: use only what is in the transcript; no interpolation of what was probably meant. If the audio-to-text garbled a section, quote the garble and mark it [UNCLEAR] rather than repairing it into something plausible.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{transcript}} | The meeting transcript | [paste the transcript or attach the recording's transcript file] |