How to Use Muse to Plan a Project

Yes. Muse, Meta's personal AI agent, can draft a complete project plan: it can research whatever the work depends on, break the effort into phases and tasks, propose timelines, and rework the plan as reality intrudes. It runs on a secure virtual machine with its own browser, so it can check vendor pages, requirements, and availability you point it to — and it works asynchronously, keeping at it after you close the app and coming back when the job is done or it needs your approval. Because it remembers what matters, you can build the plan across several conversations instead of re-explaining the project every time. Everything it does shows up in an audit trail you can review.

• Muse launched on September 8, 2026. Reuters reported that Meta's internal tests hit failure modes, and Meta's Vishal Shah acknowledged it can make mistakes and fail to finish things — treat the first plan as a strong draft, not a finished artifact.
• Muse plans and tracks in conversation; it is not project management software with boards, Gantt charts, or team workspaces. Keep the master plan in the tool your team already uses.

1. 1

   Describe the project in plain words

   One or two sentences on what 'done' looks like, the deadline, and who is involved. Muse doesn't need formal project-management vocabulary — it needs a target.

2. 2

   List what it should gather

   If the plan depends on outside facts — quotes, venue rules, lead times, permit requirements — say so explicitly so Muse uses its browser to research them.

3. 3

   Name the structure you want back

   Phases, milestones, task list, owners, risks. Vague requests produce vague plans; a section list produces something you can execute.

4. 4

   Set the approval line

   Tell Muse to check before emailing anyone, booking anything, or creating calendar events. It is designed to ask before sensitive actions, but be explicit anyway.

5. 5

   Ask for a recurring check-in habit

   Muse works asynchronously and comes back when something changes — have it re-check open items on request and report what moved instead of re-running the whole plan.

An indie app founder needs a four-week launch plan for a small iOS productivity app, with no paid-ad budget.

Goal: Plan the launch of my iOS app, Focus Timer, on October 6.
Context: I'm a solo founder. No budget for paid ads. I have a landing page, a 900-person email list, and a Product Hunt draft sitting in my notes.
Requirements:
- Phases: final QA, press and community outreach, launch day, post-launch follow-up.
- Every task needs a date and an estimate of how long it takes me.
- Include the 3 most likely failure points, such as App Store review delays.
Actions:
- Look up the current App Store review turnaround and Product Hunt launch-day best practices, and note the source for each.
- Draft but don't send: a short pitch email to two newsletters that cover small iOS apps.
Approval: Ask before sending any email or creating any calendar event.
Output: A one-page plan organized by week, plus a list of anything you couldn't verify.

• Definition of done

  Muse plans toward an outcome; a fuzzy end state produces a fuzzy task list nobody executes.

• Deadline and fixed dates

  Backwards scheduling only works if Muse knows which dates genuinely cannot move.

• People and their availability

  Owners and dependencies should reflect who can actually do the work and when, including anyone on leave.

• Budget or resource limits

  Constraints decide which tasks make the cut and what Muse should bother researching.

• Where the master plan lives

  Telling Muse the destination document lets it format output that drops straight into your existing tracker.

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 kickoff email or any outreach it drafts — Muse checks before sensitive actions like sending an email — keep it that way and read every word first.

• Creating calendar events for milestones — A wrong date on a shared calendar propagates to everyone invited; approve events before they land.

• Contacting vendors or registering for anything it finds — Research should stay research; form submissions and sign-ups have consequences that outlast the project planning session.

• Purchases against your budget — Anything that spends money should get an explicit yes from you — Muse asks before purchases, so keep the gate closed.

• ✓Feed Muse the ugly details — the deadline nobody believes, the teammate on parental leave — and let it plan around them. Its memory means corrections stick across conversations.
• ✓Ask Muse to cite where each researched fact came from, then spot-check the load-bearing ones. It is a brand-new agent, and launch coverage documented tasks it failed to finish.
• ✓Keep research and execution separate: let Muse browse and gather freely, but hold a hard approval gate on anything that emails, books, or buys.
• ✓Use the audit trail as your project log. It shows everything Muse has done and plans to do, which doubles as a record of who asked for what.
• ✓When the plan slips, paste the new reality and ask for a re-plan from today, not a postmortem. Same project, fresh dates.