How to Use Muse to Create a Daily Plan

Muse, Meta's personal AI agent, is at its best in the tight loop of a daily plan: it can read the calendar you connect, take the open work you hand it, and propose an hour-by-hour layout that respects meetings, buffers, and your stated energy curve — presented as a proposal until you approve any block that becomes a real event. Where it beats a to-do app is synthesis: it can pull deadlines from connected email so 'sometime this week' items get real due-dates, and flag the days that are mathematically doomed before you live them. Where it doesn't beat you is judgment — which task actually matters most, which meeting could've been an email — so the design intent is that you mark the one non-negotiable and it fits the rest around it. Planning the night before suits its async side too: the plan can be waiting in the morning, and if you ask, Muse can check in when the day visibly falls apart.

• A daily plan without a drop list collapses at the first surprise; make Muse produce one every time.
• Plans are only as current as the last sync — if a meeting moved overnight, confirm Muse sees the new version.
• Launch-week tooling occasionally fails to finish; if the morning plan never arrived, re-ask rather than assuming it's coming.

1. 1

   Ask the night before

   'Build tomorrow's plan at 8 pm' lets Muse work while you're off the clock, and you wake up to a proposal instead of spending your best morning hours planning.

2. 2

   Hand over the open work explicitly

   The calendar says what's booked; only you know what's open. List tomorrow's candidate tasks in the message, or point Muse at where they live.

3. 3

   Name the day's one big thing

   Give it a anchor: 'if only the QBR deck gets done, the day still counts.' Muse schedules around the anchor and protects it from meeting creep.

4. 4

   Insist on buffers and a drop list

   Require 30 minutes after any meeting that could overrun, plus a ranked list of what to abandon when the day derails. Both are cheap to ask for and priceless by 3 p.m.

5. 5

   Keep the calendar write-gated

   Let the plan live as a proposal you check over coffee; only approved blocks should become events. Reversible mornings make for better plans.

A remote customer-success manager whose Tuesday is shredded by meetings and needs a plan that can absorb the damage.

Build my plan for tomorrow. Already booked: the 9:15 team stand-up, a customer escalation call at 11:00 that will probably run long, and a 45-minute QBR rehearsal at 15:30. Around that I need to write two renewal summaries, send the quarterly health-score report, and prep questions for Wednesday's vendor demo. Assume meetings overrun. Put the deep work in my real gaps, give me a 30-minute buffer after the escalation call, and mark the one thing I should protect if the day goes sideways. Show it to me as a proposal tonight — don't add anything to my calendar, and include what to drop if the morning implodes.

• Tomorrow's fixed events

  Muse reads the connected calendar, but day-specific oddities — a call from the school, a delivery window — need saying.

• The open task list

  The raw material of the plan; unlisted work doesn't get scheduled.

• Your energy map

  When you think clearly and when you don't — so deep work lands in real focus hours, not theoretical ones.

• The day's success criterion

  One task defined as non-negotiable gives the plan a spine and the drop list a boundary.

• How rigid the plan should be

  Minute-by-minute block plans and a three-item priority list are both valid; say which you'll actually follow.

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.

• Turning plan blocks into calendar events — Until you approve, the plan is a sketch; premature event-creation clutters your calendar and misleads anyone who can see it.

• Declining or shrinking meetings to make room — Deprioritizing someone else's meeting is a social decision with consequences; the agent should propose, you decide.

• Automatic midday replans — A day that derails needs your input on what to drop — require a check-in rather than letting the plan rewrite itself.

• ✓The night-before prompt is the habit that makes this stick: same message, same structure, plan waiting at 7 am.
• ✓Ask for 'hours committed versus hours available' every time — it's the fastest early-warning system for an overloaded day.
• ✓If tomorrow is meeting-dense, ask for the 'worst-case version' of the plan: what still gets done if every meeting runs long.
• ✓Keep yesterday's drop list around; items that get dropped three days running are either delegable or not actually yours.
• ✓When the day implodes by 10 am, message Muse rather than abandoning the plan — a two-minute replan beats white-knuckling a dead schedule.