The Plan tab

Plan is where you decide the order things get built in. It shows every story in its place in the build order, release by release, split into phases. From here you start build runs: batches of stories you approve once for agents to work through.

The top of the tab says how many stories are ready: in the build order, not blocked and not yet built, so an agent could start them now. A bar shows how much of the spec is built. The Releases and Filter by status filters are the same ones Spec and Validate use.

Set the build order

With no build order yet, Plan asks No build order yet — how should we start?

• Generate build order proposes an order for every story.
• Add in map order numbers every story in the order it sits on the story map.

When stories are added later, Plan offers to Slot them in: each goes after the last story of its release, and nothing already ordered moves.

Every option is a proposal. You see the whole order, can move the new stories, and choose Save order to keep it. Or choose Copy prompt to have your own agent propose one. The in-app assistant can't write a build order.

After that, drag stories to reorder them, or use Move to release. A story with no place yet shows Not yet sequenced. See Build order.

Phases

On desktop's card view, each release is split into phases. Phase 1 holds the stories with nothing to wait for. Each later phase holds stories whose dependencies are in earlier phases. The stories in one phase don't depend on each other, so several agents can build them at once.

A phase with a run shows its state: Waiting for approval, Building with how many are built so far, Ready to review, Done, Paused or Stopped.

Run this phase

A phase is a ready-made build run. Choose Run this phase on it:

1. Check the stories listed. The run takes every unbuilt story in the phase, whatever your filters show.
2. Set Agents at once: how many of its stories may be built at the same time, from 1 to 10.
3. Choose When a story is blocked: Skip it and carry on, or Stop the run.
4. Tick Then the next phase if you want IntentDocs to line up the next phase as a run when this one is built. It never starts on its own; you approve it.
5. Choose Run with the number of stories, for example Run 4 stories.

If you can approve plans, the run is approved straight away. If you can't, it waits for someone who can. Either way you get a prompt to paste into your coding agent:

Build run R-7 with IntentDocs (project …). Call next_in_run for R-7, build the story it gives you, save your tests and report its criteria, then complete_story with the pull request. Call next_in_run again, and stop when it says the run is complete.

Paste it into more than one agent to build in parallel, up to the run's Agents at once.

New build run

The list view on desktop shows Build runs: every run on the map, newest first, each linking to its page. To make one by hand, choose New build run:

1. Pick a release. Its unbuilt stories are listed in build order.
2. Untick any you don't want, and move the rest Earlier or Later.
3. Set Agents at once and When a story is blocked.

This makes a draft. It's approved on the run's page.

The run page

Each run has a page named by its key, such as R-7. It shows the run's state and its stories in build order, each with its status, who is building it, how many must criteria pass, and its pull request.

A run stops by itself when a story is blocked and it's set to Stop the run. Skipped stories read Skipped — blocked. When every story is built or skipped, the run is ready for you to review on Validate.

Approving a run counts as the go-ahead for each story in it, whatever the project's Before agents build setting says. An agent still won't get a story until the stories it depends on are built. See Working with agents.