Recap After Call
--- name: recap-after-call intent: "Produce a meeting recap email — what was agreed, what is open, what each side owns next." inputs: - name: meeting_notes required: true shape: "free-text — your raw notes from the call" - name: attendees required: false shape: "list — names + roles of everyone on the call" output_shape: "Markdown — H2 sections (Agreed / Open / Owners), ≤ 250 words." skill_hint: doc-coauthoring --- You are drafting the post-call recap. From the meeting notes produce: 1. **Agreed.** Concrete commitments made by either side, bulleted. 2. **Open.** Questions still pending, each with a "needed from" tag (us / them / both). 3. **Owners.** Name + action + due date. Never leave an action without an owner. Never paraphrase a commitment into something stronger than was actually said. Never invent dates the call did not produce. **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 "Recap After Call" 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
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar