Meeting Agenda

Meeting Agenda

A meeting agenda is the attendee-facing structural document that sets expectations before a meeting. It answers "what will we discuss, who owns each topic, how will we spend the time, and what does done look like?" Distinct from a meeting brief, which is the user's private strategic prep; the agenda is shared with participants and focused on structure and flow.

This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract, which defines shared frontmatter, file naming, the go-mode behavioral pattern, and universal output requirements across all meeting skills.

When to Use

• Running or chairing a cross-functional working session, project kickoff, stakeholder review, or decision meeting
• Any meeting with more than three attendees or more than thirty minutes
• Recurring meeting where a rolling structure (1-on-1, team sync) needs fresh framing each time
• Mid-initiative alignment moment where explicit desired outcomes prevent drift

When NOT to Use

• The user's preparation is private and tactical (positioning, stakeholder reads, asks). Use foundation-meeting-brief instead.
• The meeting has already happened. Use foundation-meeting-recap for post-meeting summarization.
• The user wants to communicate outcomes to non-attendees. Use foundation-stakeholder-update after the meeting.

Zero-friction execution

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

1. Read all provided inputs (topic, any referenced files, attendee list, constraints)
2. Run inference on missing values (meeting type from topic keywords, duration default, objective from topic phrasing, attendee roles from context)
3. Present a brief inference summary and accept one-word go or corrections
4. Produce the agenda

If invoked with --go, skip the inference summary and produce output directly using defaults (duration 30 min, meeting type other, and so on). If the user provides all values upfront, no checkpoint appears.

Blocking questions are used only when inference confidence is actively low on a load-bearing input and no reasonable default exists. This should be rare.

Anti-meeting check

This skill opens with an explicit question: "Does this need to be a meeting, or could it be handled async?"

v1.1.0: the check now requires a positive synchronous-value statement. The meeting passes the check only when at least one of these is named:

• Tradeoff to discuss. multiple options, uncertain preference