PlaybookPrompts

Prep for a meeting along three axes

Productivity & Planning meetingspreparation

Most meeting prep is 'review notes from last meeting.' This prompt forces prep along three distinct axes: what they want, what we want, what could go sideways.

Prompt
Prep me for this meeting.

Meeting: {{MEETING_TOPIC}}
Who's there: {{ATTENDEES}}
What we know about their priorities: {{THEIR_CONTEXT}}
Our priorities: {{OUR_CONTEXT}}
Last meeting summary: {{LAST_MEETING}}

Produce three sections:
1. THEIR AGENDA: what they likely want to walk out with. The 3 questions they're most likely to ask.
2. OUR AGENDA: our must-cover, nice-to-cover, do-not-cover items. The decision we want to leave with.
3. RISK MAP: 3 ways this meeting could go sideways. For each, the early signal and our recovery move.

End with a 5-line opening I can use to set the agenda.
Variables to fill in
  • {{MEETING_TOPIC}}
  • {{ATTENDEES}}
  • {{THEIR_CONTEXT}}
  • {{OUR_CONTEXT}}
  • {{LAST_MEETING}}

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_TOPIC}}{{ATTENDEES}}{{THEIR_CONTEXT}}{{OUR_CONTEXT}}{{LAST_MEETING}}.
  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.