How to Use Muse to Plan a Party

Party planning is a research-plus-coordination problem, which is exactly the shape of task Muse handles well: it can browse for venue, menu and supplier options, build checklists and timelines as Artifacts, and track the plan over days. It can also draft invitations or group messages — though it should show you every message before anything is sent. Treat it as a very organized co-host, not an autopilot.

• Vendor bookings (caterers, rentals) need your review — prices and availability change fast
• Group messages and invites should always be approval-gated
• Taste is yours: have Muse propose 2–3 directions instead of one 'perfect' plan

1. 1

   Give the shape of the event

   Occasion, date, headcount, indoor/outdoor, and formality. 'Casual 30th birthday, 15 people, backyard, October' beats 'plan a party'.

2. 2

   Fix the budget early

   A total number, even rough. Muse can allocate across food, drinks, decorations and supplies — and will respect trade-offs you set.

3. 3

   Name the constraints that matter

   One vegan guest, no loud music after 10pm, apartment-size kitchen. Constraints shape menus and venues more than preferences do.

4. 4

   Ask for a timeline, not a list

   Request a countdown plan: what to do a week before, three days before, morning-of. Party stress lives in sequencing.

5. 5

   Gate the communication

   Let Muse draft invites or reminder messages, but require your approval before anything is sent to guests.

A nervous host is throwing a kid's birthday party for a mix of children and adults and needs the chaos structured.

Goal:
Plan a 6th birthday party for 12 kids and 10 adults, Saturday 2–4:30pm in a park pavilion.

Context:
Kids aged 4–7 with mixed attention spans. One child has a peanut allergy. October weather is a gamble.

Requirements:
Peanut-free food only.
Rain backup plan that fits in two cars.
Total budget under $250.

Actions:
Propose a 90-minute activity arc for the kids with cheap supplies.
Build a peanut-free snack and cake plan with quantities.
Draft the countdown checklist with a rain-contingency step at day-before.

Approval:
Nothing purchased or sent — draft everything for my review.

Output:
Timeline first, then food plan, then the backup plan.

• Headcount (honest version)

  Quantities, budget and space all scale from this — include the plus-ones you're expecting.

• Total budget

  Forces trade-offs early instead of a checkout surprise; Muse will allocate across categories.

• Dietary restrictions

  Allergies are safety; preferences are happiness. List both, distinctly.

• Space and equipment reality

  No oven, tiny fridge, one outlet — Muse will pick recipes and setups that actually fit.

• Vibe in three words

  'Loud, cheap, fun' and 'elegant, quiet, small' produce completely different plans.

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 invitations or group messages — Guest communication is high-visibility and hard to undo — always review drafts first.

• Booking vendors or ordering supplies — Prices and availability fluctuate; have Muse shortlist options, then you confirm.

• Adding events to shared calendars — A party on your partner's or roommate's calendar should be approved, not assumed.

• ✓Ask Muse to work backwards from the start time — service prep, ice, and setup are what hosts forget.
• ✓Request quantities per headcount explicitly ('drinks for 20, 3 hours, mostly beer and wine') — it's good at this math.
• ✓Have it plan the 'boring 15 minutes' — trash, ice refills, bathroom stock — that separate smooth parties from chaos.
• ✓For kids' parties, ask for activities with cheap, common supplies; boutique craft ideas blow budgets fast.
• ✓One day before, ask Muse to re-check the plan against weather and give you a 10-minute morning-of checklist.