How to Use Muse to Prepare a Meeting Agenda

Yes. Muse, Meta's personal AI agent, can assemble everything an agenda needs: it can browse public information about the topics or organizations involved, review email threads in the inbox you connect for unresolved items, and draft a timed agenda with owners and decisions. Because it works asynchronously, you can request meeting prep the night before and find the drafts waiting in the morning. It checks with you before sensitive actions like sending an email — so it will prepare the pre-read and the invite, but you pull the trigger. And every step it took while preparing is visible in the audit trail.

• Muse only sees what you connect or point it at. If the project status lives in a tool you have not connected, paste the notes or link the thread.
• It is days old as a product. For a high-stakes client or board meeting, verify any number Muse cites before it reaches an audience.

1. 1

   Give it the meeting's job

   One sentence: the decision or outcome that makes this meeting worth its calendar slot. Everything else in the agenda serves that sentence.

2. 2

   Point it at the inputs

   Name the email threads, documents, or pages that hold the raw material, or let Muse browse public sources for context on a company or topic.

3. 3

   Ask for a timed agenda, not a topic list

   Request minutes per item, an owner, and the decision needed for each. Muse structures this well when you are specific about the shape.

4. 4

   Have it draft the pre-read and invite — and stop there

   Muse can write both, but set the approval line clearly: nothing goes out until you have read it, no matter how good it looks.

An independent consultant is preparing a quarterly steering committee with a client who is unhappy about a slipped delivery milestone.

Goal: Agenda for the Q3 steering committee with Northwind Logistics, Thursday 10:00-10:45, six attendees.
Context: Purpose: sign-off on the revised delivery date for phase 2. The client was unhappy about the two-week slip, so rebuild trust early. They care most about cost, not features.
Requirements:
- Six items max, each with minutes, an owner, and the decision needed.
- The revised date and its rationale first; new scope requests last.
- End with agreed actions and a named owner for each.
Actions:
- Skim the project email thread from the last two weeks and list every unresolved question.
- Draft, but don't send: the invite update and a half-page pre-read covering the slip, the new date, and what changed.
Approval: Drafting only — nothing gets emailed or shared until I approve.
Output: Timed agenda, pre-read draft, invite text, and the open questions I should prepare answers for.

• The decision the meeting must produce

  Agendas without a target become status theater. Muse sequences items around a real outcome when you name one.

• Attendees and what each cares about

  Framing every item for its owner is the difference between an agenda that lands and one that gets skimmed.

• Where the raw material lives

  Email threads, notes, docs — tell Muse what to read so agenda items are grounded in reality, not invented.

• Time box and sequencing preferences

  Muse will allocate minutes, but it needs the container and any political constraints, like which topic cannot go last.

• Sensitive topics to keep off the list

  Explicit exclusions stop Muse from putting something on the agenda you would rather handle one-on-one.

For this task, it is smart to make Muse check with you before it takes certain actions. Decide your rules up front and include them in the prompt.

• Sending the invite or agenda to attendees — Muse checks before sensitive actions like sending an email — read the draft, fix the tone, then approve.

• Circulating the pre-read — Numbers in a pre-read carry your name. Verify anything Muse researched before it goes in front of other people.

• Adding or moving the calendar event — A meeting with six attendees is hard to un-invite. Check the time, title, and guest list before it lands.

• Following up with attendees on Muse's behalf — Post-meeting chase-ups touch relationships. Keep the send button yours for anything addressed to a person.

• ✓Ask for the 'decision needed' line on every item. It is the single change that turns a topic list into an agenda people prepare for.
• ✓Let Muse mine the email thread for unresolved questions — that is exactly the raw material a good agenda is made of, and it reads the connected inbox so you don't have to.
• ✓For client meetings, have Muse check recent public news about the client's company and open with one relevant, genuine item.
• ✓Draft the pre-read and the agenda from the same brief so the two documents never contradict each other.
• ✓Check the audit trail before you hit send. It shows everything Muse did while preparing — your last chance to catch a wrong number.