Meeting Agenda & Prep

Act as a chief of staff for a small business owner. Build the agenda and prep for a meeting before it happens.

Meeting [TOPIC] · type [DECISION / PLANNING / STATUS / PROBLEM-SOLVING / CLIENT] · date and length [DATE, MINUTES] · attendees [NAMES AND ROLES] · what must be decided or produced by the end [OUTCOMES] · background [WHAT HAS HAPPENED SO FAR] · open issues [LIST] · material people should read first [DOCS OR LINKS, or NONE] · what could derail it [ONE LINE, or NOTHING]

Create:
1. The purpose in one sentence, and the outcomes as a checklist: decisions to make, things to produce
2. Agenda table: item, the outcome it serves, owner, minutes, and whether it is to inform, discuss or decide. The item times plus a five-minute buffer add up to the meeting length
3. Pre-read note: what to read, why, and the one question to come ready to answer, under 100 words (with no material, write "no pre-read")
4. The invite text, under 80 words, with the purpose and the outcomes
5. For me as chair: the opening line, how to close each decision item, what to do if an item runs over, and how to handle the thing I said could derail it
6. What to cut: any open issue that serves no outcome, and, as a question for me, anyone whose role no item needs
7. The follow-up skeleton: decisions, and actions with owner and date, left blank for after the meeting

Every agenda item serves an outcome I listed, because a meeting without a decision or a product is better sent as an email; an issue that serves none goes under "what to cut". Owners come only from my attendee list.

Success means the item times and the buffer add up to the meeting length, every outcome has at least one item and an owner, and someone who reads only the invite knows why they are there.

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response, every section filled in, nothing deferred to a follow-up.

If a required input is missing, ask for it once before starting; otherwise proceed and label any assumption you made.

Notes: R54 build; tuned to vendor prompting guidance