meeting-prep-brief

$npx mdskill add Significant-Gravitas/skills-catalog/meeting-prep-brief

Use this before a named meeting, or for every meeting on a given day.

SKILL.md

.github/skills/meeting-prep-briefView on GitHub ↗
---
name: "meeting-prep-brief"
description: "Prepare a one-page meeting brief with purpose, people, history, open items, and decision needed."
triggers: ["meeting prep", "brief me", "prepare for meeting", "who am I meeting", "meeting brief"]
version: "1"
---

# Meeting prep brief

Use this before a named meeting, or for every meeting on a given day.

## Gather the context

From the calendar invite, recent mail, shared documents, and past notes,
collect the purpose, the attendees and their roles, the last time the
principal met them, what was agreed then, and anything promised since. Note
the source and date of each fact. If two contacts share a name, confirm which
one before going on.

## Write the brief

Keep it to one page, in this order:

1. the decision or outcome needed from this meeting;
2. purpose, time, place or link, and length;
3. who is attending, with one line on each;
4. what happened last time, and open items with owners;
5. documents to read first, with links.

Mark anything you could not confirm. Leave out private details from unrelated
threads.

## Questions to ask

List two or three questions that would move the decision on, drawn from the
open items. Note any topic the principal said to avoid.

Never accept, decline, or move the meeting without a clear yes. Do not invent
what someone said or agreed, and keep what you read private.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.