PlaybookPrompts

Draft a team meeting agenda anchored to real outcomes

Productivity & Planning meetingsagendadecision-making

Most meeting agendas are just topic lists with no exit criteria, so discussions run long or end without decisions. This prompt builds an agenda structured around what must be true when the meeting ends.

Prompt
You are a chief of staff helping me run a crisp, outcome-driven team meeting. Here are the details:

- Meeting purpose: {{MEETING_PURPOSE}}
- Attendees and their roles: {{ATTENDEES_AND_ROLES}}
- Duration: {{DURATION_MINUTES}} minutes
- Context or background attendees already have: {{EXISTING_CONTEXT}}
- Open questions or decisions that must be resolved: {{OPEN_QUESTIONS_OR_DECISIONS}}

1. Identify which agenda items are genuinely decision-requiring versus informational. Remove or convert any item that could be handled async.
2. For each remaining agenda item, write: (a) the specific question to answer or decision to make, (b) who leads that segment, (c) time allocation, and (d) the exit criterion — what must be true for us to move on.
3. Add a 2-minute closing segment: who captures decisions, who owns next steps, and when the next check-in is.
4. Flag any item where the right people are not in the room, or where the input needed hasn't been prepared. These should either be removed or pre-worked before the meeting.
5. Output the final agenda in a format I can paste directly into a calendar invite.
Variables to fill in
  • {{MEETING_PURPOSE}}
  • {{ATTENDEES_AND_ROLES}}
  • {{DURATION_MINUTES}}
  • {{EXISTING_CONTEXT}}
  • {{OPEN_QUESTIONS_OR_DECISIONS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{MEETING_PURPOSE}}{{ATTENDEES_AND_ROLES}}{{DURATION_MINUTES}}{{EXISTING_CONTEXT}}{{OPEN_QUESTIONS_OR_DECISIONS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.