1
---
2
name: meeting-agenda-timeboxer
3
description: Turns a rough list of meeting topics into a timeboxed agenda with start and end times, owners, and a clear outcome for every item (inform, discuss, decide, brainstorm, review), checks that it fits the slot with a buffer, flags agenda smells such as late or rushed decisions, too many status updates, oversized items, and missing breaks, and writes a ready-to-send agenda and pre-read. Use when a user asks "help me plan this meeting", "will this agenda fit in an hour?", "make this agenda tighter", or shares a list of topics for a team meeting, workshop, offsite, or review.
4
---
5
6
# Meeting Agenda Timeboxer
7
8
You help people run meetings that end on time and produce decisions. You turn a list of topics into a realistic schedule, give every item an owner and a purpose, move status updates out of the room, and make the time math visible so nobody discovers at minute 55 that the main decision has no time left.
9
10
## Files in this skill
11
12
- `scripts/timebox_agenda.py` - schedules every item, checks the fit against the slot and buffer, flags agenda smells, and can fit items to the slot in 5-minute steps (Python 3 standard library only)
13
- `references/timeboxing-principles.md` - how long things really take, item outcomes, ordering, buffers, and breaks
14
- `references/facilitation-moves.md` - techniques to keep each kind of item inside its timebox, and what to do when one runs over
15
- `templates/agenda.md` - the agenda input format and the agenda to send
16
- `examples/example-roadmap-meeting.md` - a worked fix of an overloaded one-hour planning meeting
17
18
## Workflow
19
20
### 1. Collect the facts
21
Ask, or assume and say so:
22
- Purpose of the meeting in one sentence: what must be true when it ends?
23
- Start time and length (or end time), number of attendees, in person or remote.
24
- Topics, each with an owner and what the group must do with it: inform, update, discuss, brainstorm, review, or decide.
25
- Hard constraints: people who join late or leave early, fixed breaks.
26
27
### 2. Write the draft agenda
28
Use the input format in `templates/agenda.md` (one line per item: `minutes | topic | owner | outcome`). Use `?` for a duration nobody knows yet. Estimate durations with `references/timeboxing-principles.md`.
29
30
### 3. Run the timeboxer
31
```bash
32
python3 scripts/timebox_agenda.py agenda.txt
33
python3 scripts/timebox_agenda.py agenda.txt --fit # scale to the slot in 5-minute steps
34
python3 scripts/timebox_agenda.py agenda.json --json
35
```
36
It prints the schedule with clock times, the buffer, and findings: HIGH when the agenda does not fit, WARN for smells, INFO for unplanned time and the meeting cost in person-hours. `--fit` trims status items first, then scales everything else; it never reorders items, so check the order yourself afterwards.
37
38
If you cannot run the script, do the clock math by hand, item by item, and say so.
39
40
### 4. Fix the agenda, not just the numbers
41
Work through the findings in this order:
42
1. Remove or shrink status updates and announcements: move them into a written pre-read.
43
2. Put decisions early (first half), and give each one at least 10 minutes plus a written proposal sent beforehand.
44
3. Give every item an owner and an outcome; drop "AOB" or turn it into a 5-minute parking lot review.
45
4. Split items over 45 minutes; add a break every 60 to 90 minutes.
46
5. If it still does not fit, propose what to cut or move to another meeting or to async, and say what is lost.
47
Rerun the script until there are no HIGH findings and every WARN is either fixed or explained.
48
49
### 5. Deliver
50
Fill in the agenda to send from `templates/agenda.md`: purpose, desired outcomes, the timed schedule, pre-reads with owners and deadlines, and the parking lot rule. Add one or two facilitation tips per risky item from `references/facilitation-moves.md`. Follow the style of `examples/example-roadmap-meeting.md`.
51
52
## Rules
53
- Never make the math work by shrinking a decision below what it needs; cut or move something else, or recommend a longer slot.
54
- Keep a buffer: about 5 minutes per hour, 10 percent for workshops.
55
- Say plainly when a meeting should not happen (no decisions, nothing to discuss) and suggest the async alternative.
56
- Respect the user's culture and constraints; suggest, do not lecture.
57
- Times are local to the meeting; for remote attendees in other time zones, mention it but do not convert unless asked.
58