Plan

Use Plan before a larger build. Shape the goal into a spec, break it into visible tasks, and make the product decisions clear enough that the factory can run without guessing. Plan opens with two panes: a project docs browser on the left and the board on the right.

#Project docs

The docs pane browses your project’s durable knowledge files: everything under docs/, plans/, and skills/, plus the root README.md and AGENTS.md. Drill into a folder to see its files, or type in the search box to find one by name across the whole project.

Open a file to read it as rendered markdown. From the header you can:

• Toggle to edit mode and change it inline, then Save.
• Press New and name a file, for example profile-spec.md, to start a fresh doc.
• Open in editor to move it into the full Dev editor.

When you hand a goal to the factory, the Manager writes the spec it derives into a doc here, so the plan the agents work from is a file you can read and edit, not a hidden prompt.

#The board

The board is a kanban of tasks moving through backlog, in progress, review, and done. Work that is ready for an agent to pick up sits in the backlog column, and done stacks under review, so the whole run reads at a glance.

• Press Create task (the + in the board header) to add one. A task pane opens where you name it and describe the outcome.
• Drag a card between columns to move it, for example from backlog to in progress.
• Click a card to open its detail beside the board and edit it.

Once the factory is running, the board fills itself: each task an agent picks up moves across the columns on its own, and the chat button on an active card jumps to that agent’s chat in the Factory section.

#From plan to build

A good plan is a short spec plus a set of tasks that name outcomes rather than files. Write or refine the spec in the docs pane, let the board hold the tasks, then hand the goal to the factory and watch it execute. The build loop itself, from framing the goal to landing the result, is in Factory.