Meeting Agenda Timeboxer
--- name: meeting-agenda-timeboxer 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…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from f.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
--- name: meeting-agenda-timeboxer 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. --- # Meeting Agenda Timeboxer 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. ## Files in this skill - `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) - `references/timeboxing-principles.md` - how long things really take, item outcomes, ordering, buffers, and breaks - `references/facilitation-moves.md` - techniques to keep each kind of item inside its timebox, and what to do when one runs over - `templates/agenda.md` - the agenda input format and the agenda to send - `examples/example-roadmap-meeting.md` - a worked fix of an overloaded one-hour planning meeting ## Workflow ### 1. Collect the facts Ask, or assume and say so: - Purpose of the meeting in one sentence: what must be true when it ends? - Start time and length (or end time), number of attendees, in person or remote. - Topics, each with an owner and what the group must do with it: inform, update, discuss, brainstorm, review, or decide. - Hard constraints: people who join late or leave early, fixed breaks. ### 2. Write the draft agenda 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`. ### 3. Run the timeboxer ```bash python3 scripts/timebox_agenda.py agenda.txt python3 scripts/timebox_agenda.py agenda.txt --fit # scale to the slot in 5-minute steps python3 scripts/timebox_agenda.py agenda.json --json ``` 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. If you cannot run the script, do the clock math by hand, item by item, and say so. ### 4. Fix the agenda, not just the numbers Work through the findings in this order: 1. Remove or shrink status updates and announcements: move them into a written pre-read. 2. Put decisions early (first half), and give each one at least 10 minutes plus a written proposal sent beforehand. 3. Give every item an owner and an outcome; drop "AOB" or turn it into a 5-minute parking lot review. 4. Split items over 45 minutes; add a break every 60 to 90 minutes. 5. If it still does not fit, propose what to cut or move to another meeting or to async, and say what is lost. Rerun the script until there are no HIGH findings and every WARN is either fixed or explained. ### 5. Deliver 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`. ## Rules - Never make the math work by shrinking a decision below what it needs; cut or move something else, or recommend a longer slot. - Keep a buffer: about 5 minutes per hour, 10 percent for workshops. - Say plainly when a meeting should not happen (no decisions, nothing to discuss) and suggest the async alternative. - Respect the user's culture and constraints; suggest, do not lecture. - Times are local to the meeting; for remote attendees in other time zones, mention it but do not convert unless asked. FILE:references/timeboxing-principles.md # Timeboxing principles ## Every item needs an outcome | Outcome | What the group does | Typical time | Notes | |---|---|---|---| | inform | Hear something, ask a clarifying question | 2 to 5 min | Better as a written pre-read. | | update | Status from people or teams | 1 to 2 min per person | Usually async; keep only blockers live. | | discuss | Explore a topic, share views, no decision yet | 10 to 20 min | Say what the discussion feeds (a decision next week, a doc). | | brainstorm | Generate options | 15 to 30 min | Needs a framed question and a method (silent writing first). | | review | Give feedback on a draft, design, or plan | 15 to 40 min | Send the material beforehand; agree what kind of feedback is wanted. | | decide | Choose between options and commit | 10 to 30 min | Needs a written proposal, the options, the decision maker, and the decision rule. | | break | Rest | 5 to 15 min | Every 60 to 90 minutes. | If an item has no clear outcome, ask: "What will be different after this item?" If the answer is "nothing", cut it. ## How long things really take - Introductions: about 1 minute per person for a new group, 0 for a regular team. - Each person speaking once on a topic: about 1.5 to 2 minutes per person. Eight people, one round, is 15 minutes. - Screen sharing and getting started: 2 to 3 minutes, more for remote meetings with new tools. - A decision with real disagreement: double the estimate, or split it into "discuss" now and "decide" next time. - Items late in the agenda run faster but worse: people rush or leave. ##…
Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
Based on my prior interactions with ${person}, give me 5 things likely top of mind for our next meeting.
-
Summarize the meeting transcript by performing the following tasks: - **State the Meeting Objective**: Begin with a brief paragraph (2-3 sentences) explaining the overall objective or purpose of the meeting based on…
-
Time Zone Meeting Slot Finder
Prompts--- name: time-zone-meeting-slot-finder description: Finds fair meeting times for distributed teams. Takes each participant's IANA time zone, working days and hours, how far they will stretch, holidays and blocked…
-
Default Meeting Summary
PromptsYou are a helpful assistant. The following is a meeting transcript. Please: 1. Summarize the meeting in 1–2 paragraphs. 2. List clear and concise action items (include who is responsible if available). Return format…
-
Act as a developer tasked with building a meeting room booking web app using PHP 7 and MySQL. Your task is to develop the application step by step, focusing on different roles and features. Your steps include: 1…
-
Create a beautiful, ultra-detailed 3D animated family short film featuring a cute toddler boy with fluffy golden-blond hair, big expressive blue eyes, rosy cheeks, and blue-and-white striped pajamas. He interacts…