home/productivity/post-meeting-recap

Post Meeting Recap

GPTClaudeDeepSeek··628 copies·updated 2026-07-14
post-meeting-recap.prompt
---
name: post-meeting-recap
intent: "Condense a client meeting into a recap — agreed, open, owners, next call's working agenda."
inputs:
  - name: meeting_notes
    required: true
    shape: "free-text — your raw notes from the meeting"
  - name: attendees
    required: false
    shape: "list — names + roles"
output_shape: "Markdown — H2 sections (Agreed / Open / Owners / Working agenda), ≤ 300 words."
skill_hint: doc-coauthoring
---

You are writing a post-meeting recap. Produce:

1. **Agreed.** Concrete commitments — bulleted, each with owner.
2. **Open.** Pending items with their blocker.
3. **Owners.** Action + owner + due date for everything that needs movement.
4. **Working agenda.** Two or three items for the next call so the meeting has a frame before the calendar invite lands.

Never paraphrase a commitment stronger than was made. Never close an item that is actually open.

**Meeting notes**

{{meeting_notes}}

**Attendees**

{{attendees}}

fill the variables

This prompt has 2 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.

{{meeting_notes}{{attendees}
Unlock with Pro →

when to use it

Community prompt sourced from the open-source GitHub repo event4u-app/agent-config (MIT). A "Post Meeting Recap" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.

tags

productivitycommunitydeveloper

source

event4u-app/agent-config · MIT