Meeting Brief

Meeting Brief

A meeting brief is the user's private strategic preparation document for a meeting where context, stakes, or positioning matter. It captures what the user needs to know, what they want to accomplish, who they are engaging with, and how to navigate the conversation. This is strategic prep, not meeting structure, which keeps it distinct from a meeting agenda.

This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract.

When to Use

• Walking into a stakeholder review, exec briefing, or negotiation-adjacent conversation
• First meeting with a new stakeholder where relationship calibration matters
• A meeting where the user needs something from others (capacity commitment, decision, approval)
• Any conversation where specific positioning, messaging, or risk navigation is required

When NOT to Use

• Preparing the agenda attendees will see. Use foundation-meeting-agenda instead.
• Post-meeting summarization. Use foundation-meeting-recap.
• The meeting is low-stakes and well-trodden (recurring team sync, standup). A brief is overhead for these; the agenda alone is sufficient.

Zero-friction execution

Per the family contract, this skill never blocks on interrogation. Default flow:

1. Read all provided inputs (topic, attendees, prior recaps, stakeholder summaries, user's primary ask)
2. Auto-discover related artifacts via project or topics frontmatter match
3. Run inference on missing values (stakeholder positions from prior recaps, primary ask from topic, top-3 goals from meeting type)
4. Present a brief inference summary and accept one-word go or corrections
5. Produce the brief

If invoked with --go, skip the inference summary. If the user provides all values upfront, no checkpoint appears.

The skill runs on inferred stakeholder positions with low-confidence flags when no stakeholder summaries are provided; it does not block on missing inputs.

Anti-meeting check

This skill opens with the shared anti-meeting check. see foundation-meeting-agenda for the full check.

v1.1.0: the check requires a positive synchronous-value statement (tradeoff to discuss, conflict to resolve, co-creation, relationship-building, or blocker escalation). Brief-prep scenarios most often pass because they typically involve navigating stakeholder positions or negotiation dynamics. which qualify as "conflict to resolve" or "relationship-building." But the check still runs, and if no synchronous value is named, the skill recommends the async alternative before producing a brief.