Meeting Agendas SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as meeting-agenda/SKILL.md.

---
name: meeting-agenda
description: "Write agendas that make meetings shorter and more useful: a check of whether to meet at all, purpose and outcome, items framed as decisions, discussions or input with owners and time boxes, decisions first, pre-reads for information, the right attendees, recurring meeting rules and facilitator tips. Use whenever someone needs a meeting agenda, wants shorter or more productive meetings, is planning a kickoff, team meeting, client or board meeting, or wants to fix a recurring meeting that has lost focus."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/meetings-calendar/meeting-agenda/
  category: productivity
  subcategory: meetings-calendar
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-13"
---

# Meeting Agendas

Meetings without agendas drift. People arrive unsure why they are there, the loudest topic takes the time, decisions are deferred and the meeting ends with another meeting. A good agenda does more than list topics: it states the purpose, the outcome expected for each item, who leads it, how long it gets and what people must read beforehand. Many teams also find that a clear agenda reveals when a meeting is not needed at all.

This skill writes agendas that make meetings shorter and more useful: a purpose and outcome, items framed as questions or decisions, owners and time boxes, pre-reads, the right attendees, and a check of whether the meeting should happen at all or could be handled in writing.

## Operating principles
1. **Purpose and outcome first.** If the meeting has no clear outcome, it may not need to happen.
2. **Items as questions or decisions.** "Decide the launch date" beats "Launch".
3. **Time boxes.** Each item has minutes and an owner; the total fits the slot with a few minutes spare.
4. **Pre-reads for information.** Updates are read beforehand; meeting time is for discussion and decisions.
5. **Only the people needed.** Invite those who decide, contribute or must hear it live; inform the rest afterwards.

## Item types
| Type | Label | Example |
|---|---|---|
| Decision | Decide | Decide between vendor A and B |
| Discussion | Discuss | Discuss options to cut onboarding time |
| Input | Get input | Get input on the draft pricing page |
| Information | FYI (pre-read) | Q3 results (read before the meeting) |
| Planning | Plan | Agree owners and dates for next sprint |

## When to use, and when not to
Use it for team meetings, project kickoffs, decision meetings, client meetings, workshops, board or committee meetings and recurring meetings that have lost focus.

Don't use it for short informal chats or for full-day workshop design (`workshop-facilitation`).

## Inputs
- Meeting goal and audience.
- Topics people want to cover.
- Length of the slot.
- Decisions needed and who makes them.
- Documents people should read first.

## Workflow

### Step 1. Check the meeting is needed
If the goal is only to share information, suggest a written update. If several people need to decide or solve a problem together, keep the meeting.

### Step 2. Write the purpose and outcome
One sentence each: why we are meeting and what will exist at the end.

### Step 3. Frame the items
Turn topics into questions or decisions, label each type, and order them: decisions and hardest topics early while energy is high.

### Step 4. Assign owners and times
One owner per item; minutes per item; leave about 5 minutes for wrap-up and actions.

### Step 5. Add pre-reads
Link documents with a note on what to look for; send at least 24 hours ahead for important meetings.

### Step 6. Choose attendees
Decision makers and contributors; mark optional attendees; note who will receive notes only.

### Step 7. Send with the invite
Put the agenda in the calendar description so it travels with the event.

## Agenda template
```
<Meeting name> | <date> | <length> | <video link or room>
Purpose: <why we are meeting>
Outcome: <what we will have at the end>
Pre-reads: <link> (look at: <what>)

1. Decide: <question> | <owner> | 15 min
2. Discuss: <question> | <owner> | 15 min
3. Get input: <question> | <owner> | 10 min
4. Actions and owners | facilitator | 5 min

Attendees: <required> | Optional: <names> | Notes to: <names>
```

## Recurring meetings
- Keep a standing structure (wins, metrics, decisions, blockers, actions).
- Collect items in a shared document beforehand; drop the meeting if nothing is added.
- Review recurring meetings quarterly: shorten, reduce frequency or end them.
- Start with actions from last time.

## Output format
```
1. Recommendation: meet, shorten, or handle in writing (with reason)
2. Agenda (template above)
3. Pre-read notes
4. Attendee list with roles
5. Calendar description text, ready to paste
```

## Time box guide
| Meeting length | Items | Wrap-up |
|---|---|---|
| 15 minutes | 1 to 2 | 2 minutes |
| 30 minutes | 2 to 3 | 5 minutes |
| 60 minutes | 3 to 5 | 5 to 10 minutes |
Default to 25 or 50 minutes instead of 30 or 60 so people have a break between meetings.

## Should this be a meeting?
| If the goal is to... | Better format |
|---|---|
| Share an update | Written update or short recorded video |
| Collect opinions on a document | Comments in the document with a deadline |
| Make a decision with several stakeholders | Meeting with a pre-read |
| Solve a complex or sensitive problem | Meeting |
| Build a relationship or onboard someone | Meeting |
| Brainstorm widely | Silent written ideas first, then a short meeting |

## Agendas for client meetings
Share a short version with the client in advance: purpose, two or three topics and the outcome hoped for, inviting them to add items. Keep internal notes, such as negotiation limits or sensitive context, in a separate brief. Clients often respond well to being asked what they want from the time.

## Writing items as questions
| Topic | Question |
|---|---|
| Budget | Do we approve the extra \u00a35,000 for Q4 events? |
| Hiring | Which two candidates go to final interviews? |
| Launch | Do we launch on 21 October or wait for the integration? |
| Process | How do we cut review time from five days to two? |
Questions make it obvious when an item is finished: when it has an answer.

## Using an AI agent
The agent can draft the agenda from the invite, related emails and the last meeting's open actions, suggest which items should be pre-reads, check the total time against the slot and paste the agenda into the calendar event. The organiser approves before it is sent.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Too many items for the slot | Move information to pre-reads; split into two meetings or prioritise |
| No decision maker attending | Reschedule or reframe as input gathering |
| Large audience (all-hands) | Questions collected in advance; clear sections; recording |
| Cross-time-zone team | Rotate meeting times; record; shorter agenda |
| Client meeting | Share a lighter version with the client; keep internal notes separate |
| Sensitive topics | Mark items for a smaller group or separate session |

## Handoffs to related skills
- Preparation for important meetings: `meeting-prep-brief`
- Notes and actions: `meeting-notes-actions`
- Follow-up emails: `meeting-follow-up`
- Decision meetings: `decision-meetings`
- Replacing meetings with written updates: `async-updates`

## Worked example
A product team's weekly meeting ran 60 minutes and rarely decided anything. The new agenda moved metrics to a pre-read, framed three items as decisions (release scope, a pricing test, support rota), gave each an owner and 10 to 15 minutes, put decisions first and ended with five minutes for actions. Items were collected in a shared document by Monday noon, and the meeting was cancelled when fewer than two items were added. Meetings fell to 30 minutes and decisions were made in most sessions.

## Common mistakes
- Agendas that are lists of nouns.
- Status updates read aloud.
- No time boxes, so the first item eats the meeting.
- Inviting everyone "just in case".
- Sending the agenda minutes before the meeting.

## Facilitator tips
- Restate the purpose and outcome in the first minute.
- Keep to time boxes; park off-topic points in a list.
- End each item by naming the decision or next step.
- Close with actions, owners and dates read aloud.

## Self-check before you answer
- Is there a clear purpose and outcome?
- Is every item a question or decision with an owner and time?
- Are information items pre-reads?
- Was the option of not meeting considered?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/meetings-calendar/meeting-agenda/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.