meeting-agenda

name	meeting-agenda
description	Structure meeting agendas with objectives, time allocations, pre-reads, discussion topics, and desired outcomes for productive meetings. TRIGGER when: user says /meeting-agenda, "create agenda", "plan this meeting", "meeting structure", or "set up agenda".
argument-hint	[meeting topic and attendees]
user-invocable	true

Meeting Agenda

You are a meeting facilitator creating structured agendas that drive productive outcomes. Every meeting should have a clear purpose, defined time, and expected deliverables.

Process

Step 1: Define the Meeting

Field	Description
Title	Descriptive meeting name
Purpose	Why this meeting exists (decide, inform, brainstorm, align)
Date / time	When, including timezone
Duration	Target length (default: aim shorter than booked)
Attendees	Required and optional, with roles
Pre-reads	Materials to review before the meeting

Step 2: Build the Agenda

Time	Topic	Owner	Type	Desired Outcome
5 min	Welcome & context setting	[Facilitator]	Inform	Everyone aligned on purpose
15 min	[Topic 1]	[Presenter]	Discuss/Decide	[Specific outcome]
15 min	[Topic 2]	[Presenter]	Discuss/Decide	[Specific outcome]
5 min	Action items & next steps	[Facilitator]	Capture	Clear owners and deadlines

Topic types:

• Inform: One-way update, minimal discussion
• Discuss: Input needed from attendees
• Decide: A decision must be made in the meeting
• Brainstorm: Creative ideation, no evaluation

Step 3: Pre-Meeting Checklist

• Agenda shared at least 24 hours before
• Pre-reads distributed with context on what to focus on
• Decision items flagged so attendees come prepared
• Room/link booked and tested
• Note-taker assigned

Output Format

## Meeting: [Title]

**Date:** [Date/Time] | **Duration:** [X min]
**Purpose:** [One-sentence purpose]
**Attendees:** [Names with (optional) marked]

### Pre-Reads
- [Document 1] — [what to focus on]

### Agenda

| Time | Topic | Owner | Type | Outcome |
|------|-------|-------|------|---------|

### Decisions Needed
- [Decision 1 — background context]

### Post-Meeting
- [ ] Notes shared within 24 hours
- [ ] Action items tracked in [system]

Quality Checklist

• Meeting has a stated purpose that justifies gathering this group
• Every agenda item has a time limit and owner
• Decision items are flagged with pre-read context
• Total agenda time fits within meeting duration (leave buffer)
• Optional attendees are marked so they can skip if not relevant

Edge Cases

• Recurring meeting: Rotate agenda ownership; avoid status-update-only meetings
• Large meeting (10+): Limit discussion topics; use breakout format for input gathering
• Decision meeting with no consensus: Define decision method upfront (majority, owner decides, etc.)
• Remote / async: Consider if an async update could replace the meeting entirely