Prepare for any meeting in minutes: build a 5-minute brief (purpose, people, your goal, questions, materials), research attendees, and capture decisions and action items afterward. Use when someone asks to prep for a meeting, has a big call coming up, or wants a debrief after one.
Installs into .claude/skills of the current project.
Are you the author of Meeting Prep Brief?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/aicodedecode-meeting-prep-brief)
---
name: meeting-prep-brief
description: Prepare for any meeting in minutes: build a 5-minute brief (purpose, people, your goal, questions, materials), research attendees, and capture decisions and action items afterward. Use when someone asks to prep for a meeting, has a big call coming up, or wants a debrief after one.
category: everyday-assistant
---
## Overview
Most people walk into meetings with nothing but a calendar invite and hope.
A five-minute brief changes the dynamic entirely: you know why the meeting
exists, who matters in it, what you personally want from it, and what you
are going to ask. The assistant becomes your chief of staff — taking the
scraps of information you have (a subject line, a name, a half-remembered
context) and turning them into a clear, skimmable brief before the meeting,
and into clean notes afterward. Over time this habit compounds: meetings
stop feeling like interruptions and start feeling like things you prepared
to win. The investment is tiny — five focused minutes — and the return is
confidence, better questions, and far fewer "wait, what did we decide?"
follow-ups.
## When to use
- You have a meeting coming up and only a vague title to go on — say:
"I have a meeting tomorrow with X about Y, prep me."
- It is an important meeting (job interview, sales call, negotiation,
first client intro) where showing up prepared visibly matters.
- You need to research the other attendees — their roles, background,
likely motivations and concerns.
- The meeting just ended and your notes are a mess — you want decisions
and action items extracted cleanly.
- You are walking into a recurring meeting and want a quick "what is my
goal this time" reset instead of drifting through another status round.
- You have been invited to something and are not sure you even need to
attend — a brief can reveal that the answer is no.
## Core concepts
- **The 5-minute brief:** a one-page structure with five blocks — *Purpose*
(why is this meeting happening?), *People* (who is in the room and what
do they care about?), *Your goal* (what does success look like for you?),
*Questions to ask* (3–5 prepared questions), and *Materials* (anything to
bring, read, or share). If the assistant cannot fill a block from what
you give it, it asks for just that block — no twenty-question intake.
- **People before content:** most meetings are decided by relationships,
not agendas. Researching attendees — role, tenure, what they own, recent
public activity — tells you where their incentives point and what
objections they are likely to raise. A quiet stakeholder with veto power
matters more than the loudest voice in the room.
- **One goal per meeting:** "have a good discussion" is not a goal. A goal
is a decision, a commitment, or information you will walk out with. The
assistant should push you to name one, even a small one, because an
explicit goal changes how you listen.
- **Questions are leverage:** prepared questions signal competence, surface
hidden constraints early, and give you something productive to do when the
conversation stalls. The best questions are the ones the other person has
thought about but never been asked — they make people feel understood.
- **Capture beats recall:** human memory of meetings is notoriously
optimistic — everyone remembers agreeing on different things. Capturing
decisions and action items (with owners and deadlines) immediately
afterward is where the prep pays off, turning talk into accountability.
- **The pre-read test:** if you were sent materials, the brief should tell
you what to actually read versus skim. Ten focused minutes on the right
three pages beats an hour of dutiful cover-to-cover reading.
## Practical workflow
Everything happens in conversation — the assistant asks short questions,
you answer in fragments, it does the organizing.
**Before the meeting:**
1. **You say:** "Prep me for my meeting with [name/company] tomorrow at
[time] about [topic, even loosely]." Attach or paste the invite text if
you have it. That alone is enough to start.
2. **The assistant asks what it needs:** who you are in this context (job
seeker? vendor? manager?), what you already know about the attendees,
and what outcome you want. Keep answers short — bullet fragments are
fine. It will not interrogate you; three questions max before drafting.
3. **It drafts the brief** in the five blocks. If it can research the
attendees (company websites, public profiles, recent news), it summarizes
only the useful bits: what they own, what they are likely measured on,
any recent public signals like a launch, a funding round, or a job
change. Noise gets cut; you get the three facts that change how you
approach them.
4. **You iterate:** "The goal is too soft — I actually need them to agree
to the timeline." The assistant sharpens the goal and re-derives the
questions from it, so the questions serve the goal instead of floating
free. One or two rounds of this is usually enough.
5. **It ends with a pocket version:** your 1 goal and 3 questions in under
10 lines, for a glance on your phone right before you walk in. The full
brief stays available if you want the detail.
**After the meeting:**
6. **You dump your raw notes** — however messy, a voice-memo transcript or
scribbles. The assistant extracts: decisions made, action items with
owners and deadlines, open questions, and anything that contradicted
your pre-meeting assumptions (that last part is gold for next time).
7. **It flags follow-ups:** "You said you would send the proposal by
Friday — want a reminder?" and offers a one-paragraph summary you can
forward to attendees or file. Sending a crisp recap within a day also
quietly establishes you as the organized one.
**Recurring meetings:** once the assistant knows the standing meeting, it
can prepare a fresh brief each time from the latest context — "based on
last week's decisions, this week's goal should probably be X" — so even
routine meetings get sharper.
## Common pitfalls
- **Preparing content but not people.** The best-prepared deck loses to the
attendee whose incentives you never considered. Always spend at least a
minute on who is in the room and what each person needs.
- **Walking in with no personal goal.** If you do not define success, the
meeting defines it for you — usually as "attend." Even "learn whether
they are serious" is a goal, and it changes what you notice.
- **Over-researching.** Ten minutes of attendee research is enough for most
meetings. A full dossier is for negotiations and interviews; do not let
prep become procrastination dressed as diligence.
- **Treating the brief as a script.** The brief is scaffolding, not a
teleprompter. If the conversation goes somewhere better, follow it — the
prepared questions are still there when you need them.
- **Skipping the capture.** The value of a debrief decays fast. Dump your
notes the same day; tomorrow you will misremember what "yes" meant, and
next week you will have invented a different meeting entirely.
- **Confusing the assistant's research with facts.** Public-profile
summaries are starting points, and profiles go stale. Verify anything
load-bearing (their actual title, their decision authority) in the room
rather than acting on it blindly.
- **Prepping for meetings you should decline.** Sometimes the brief reveals
the meeting has no purpose you can influence. The bravest outcome of good
prep is asking to be excused — or sending your input async instead.