When a project's plan is settled, set its status to Ready. This tells builders they can pick it up.

Check the plan first

Grove doesn't check the plan for you when you change the status. Before you set Ready, check that:

The project has its outcomes. See Write a project's outcomes.
No heading in the Requirements says Not yet discussed.
Every Open: line left is one you agree builders can work around. See Settle the requirements.

If you're not sure, ask Grove: "Is P-003 ready to build?"

Set the status

The status menu is only active when the project has a Requirements document.

You can also set it in these places:

The Scope document. Each project card has the same status menu.
Work › Projects. Click the project's Status cell. In tables, this status shows as Ready to build.
The chat. Ask Grove, such as "Set P-003 to ready to build." Grove tells you the current and new status, and waits for your yes.

Anyone in the workspace can change a status, in either direction.

Grove doesn't send a notification when a project becomes ready. Tell your builders, or let them find it:

A builder's coding agent can list the projects that are ready to build, with grove project list --status ready.
In Work › Projects, anyone can filter by Status to see the projects that are Ready to build.
On the Queue, a new teammate can click See what's ready to be built, and Grove lists up to five ready projects.

Builders need an invitation to your workspace and the Grove CLI. Send them Quick start for builders.

When a builder picks up the project with the Grove CLI, the status moves to Building by itself. The builder is also added to the project's Members.
When the project moves to Building, its initiative moves to Building too.
When the work has shipped and you've checked it, set the project to Built yourself. Grove never sets Built. See Review shipped work and mark outcomes done.

If the plan changes after a builder starts, the builder's agent sees that the project changed, and can pull the latest plan.