Every piece of work in Grove follows the same path: from an idea, to a plan, to code, to a check that what shipped is what you decided. Statuses show where each initiative and project is on that path. Grove moves some statuses for you. You move the rest.
The path at a glance
Stage | What happens | Who does it |
1. Idea | You describe a new capability, and Grove creates an initiative. | You |
2. Plan | Grove asks questions, then writes the Opportunity and Solution and the Scope with you. The work is split into projects. | You and Grove |
3. Details | Grove works through each project's Requirements with you, one decision at a time. | You and Grove |
4. Build | A builder picks up a ready project in their coding agent and builds it. | Builders |
5. Check | Grove reads the merged code and shows which outcomes look done. You make the final call. | Grove, then you |
Initiative statuses
An initiative holds a theme of work and all of its projects.
Status | What it means | How it gets there |
Unplanned | The idea is captured, but there is no plan yet. | Every new initiative starts here. |
Planning | The plan is being written. | Automatic, when the first project moves to Planning. |
Building | At least one project is being built. | Automatic, when a project moves to Building. |
Built | The work is finished. | You set it. |
An initiative has no "Ready to build" status. Readiness belongs to each project.
Project statuses
A project is a slice of work that can ship on its own.
Status | What it means | How it gets there |
Unplanned | The project exists, but nothing is written yet. | Every new project starts here. |
Planning | Its outcomes or requirements are being written. | Automatic, the first time one of its plan documents has real content. |
Ready to build | The plan is settled, and a builder can pick it up. | You set it. On a project's page, this status shows as Ready. |
Building | A builder is working on it. | Automatic, when a builder picks it up with the Grove command-line tool. |
Built | The work shipped, and you checked it. | You set it. |
To change a status, click the status next to Project status on the project's page, and pick a new one. You can also ask Grove to change it. You can move a status in either direction at any time.
Note: If you set an initiative's status yourself, Grove stops moving it to Planning for you. Grove still moves it to Building when one of its projects starts building.
Outcome tags
Each project lists 1 to 3 outcomes, in most cases. An outcome is something a user can do once the project ships. Next to each outcome, a tag shows how far the work has come.
Tag | What it means |
Nothing linked | No pull request is linked to this outcome yet. |
Building | Work is linked and in progress. Or the builder says it's finished, and Grove hasn't confirmed it yet. |
Ready for review | Grove read the merged code and thinks the outcome is done. Take a look. |
Needs you | The builder says the outcome is done, but Grove's reading of the code doesn't agree. You decide. |
Done | You ticked the outcome's box. Only a person can mark an outcome done. |
Grove never marks an outcome done or a project built by itself. It shows you the evidence, and you make the call.
Outcome tags need GitHub connected to your workspace. Without GitHub, every outcome shows Nothing linked until you tick it done.
Related articles
Track progress and delivery
Review shipped work and mark outcomes done