Planning a launch over two weeks

Research and writingFounder running a launch from the terminal

Launch work spread over two weeks: checklist, posts, emails, a site change. Every morning we explained the plan again.

How do I track a two-week launch plan so my AI agent knows what's done each morning?

Hold the launch as parts with ArcRoom's split_task, and complete each part in the playbook as it's finished. Each morning's session then sees what's done and what's next, so you don't explain the plan again. ArcRoom tracks the work the agents did. It isn't a project management tool.

Also asked as: I re-explain my launch plan to my AI agent every morning. How do I stop? · How do I split a big project into parts an AI agent can track? · Can an AI agent pick up a multi-week plan where yesterday's session stopped?

The work

split_task holds the launch as parts.

ArcRoom keeps
  • Split into parts
The next agent gets

split_task → launch

Step by step

  1. split_task holds the launch as parts.
  2. Each finished part is completed in the playbook.
  3. Each morning's session sees what's done and what's next.

What the agent sees

split_task → launch
✓ landing copy ✓ waitlist email ○ Product Hunt post ○ friends list DMs

Compared with today's tools

Notion or Linear checklist + a morning paste

Keep the launch checklist in Notion or Linear and paste its current state into the agent each morning.

Setup
30 min
Ongoing
~10 min a day to update and paste

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min (npx arcroom init)
Ongoing
None

A project tool is the right home for the plan; ArcRoom adds what the agents did yesterday without the daily paste.

Where it stops

ArcRoom tracks the work the agents did. It isn't a project management tool.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in research and writing