The problem
You are hosting six people on Saturday. Muse plans the menu, remembers who cannot eat what, and handles the invitations.
Before you start
- Read and modify your calendar
- Send messages on your behalf
Steps
- Tell Muse the date, headcount and vibe, such as casual and Italian-ish.
- Muse suggests a starter, main and dessert scaled to six, plus a shopping list and a prep timeline working backward from 7pm on Saturday.
- It recalls dietary restrictions from past conversations. If you once mentioned that Priya is vegetarian and Dan is gluten-free, it flags the dishes that need adapting without you re-entering anything.
- It drafts the invitation messages; you approve each one and it sends them through your connected messaging or email.
- It can turn the whole plan into a printable checklist you keep on your phone in the kitchen.
The result
Memory cuts both ways. Tell Muse to forget something and verify that it did. The upside is that the second dinner party is far easier than the first. Approval gates: Menu approval, then per-invite approval before anything sends.
Questions about this workflow
What does this workflow do?
Give Muse the date, headcount and vibe. It plans a scaled menu, remembers who cannot eat what.
What prompt does this workflow use?
I'm hosting a dinner party Saturday for 6. Plan an Italian-ish menu, build the shopping list and a prep timeline, and draft the invites. Remember everyone's dietary stuff.
How do I use this workflow?
Copy the prompt from this page into Muse and adjust the details to your situation. The result above is what the author got. Every workflow here is free to use; you just need access to Muse, and if you do not have an invite yet you can claim a community code on the homepage.
Report this workflow
Be one of the first to post your Muse workflow here. Add your own and become the person people follow.
Discussion
No comments yet
Sign in to join the discussion