Grove helps product teams decide what to build, and know it got built. It drives your product process from the first idea to shipped code, and pulls you in for the decisions that matter.
Why Grove exists
AI made writing code much faster. Deciding what to build did not get faster, and neither did checking what got built.
Coding agents build exactly what they are told. When a plan is vague, the agent fills the gaps with guesses, and those guesses ship. Grove works on both sides of the build. Before it, Grove helps you make clear decisions. After it, Grove shows you whether what shipped is what you decided.
How Grove works
1. Describe a new capability
Click New work, give the idea a name, and describe it in a few sentences. Say what you want customers to be able to do, who it's for, and why it matters now. A rough description is fine. You can also attach notes, research, or customer feedback. Grove creates an initiative to hold the work.
2. Let Grove vet the idea
Before Grove writes anything, it puts your idea through a round of questions. Some questions clarify what you intend and fill in missing details. Others challenge you: Grove points out assumptions that look risky, and plans that don't fit your product strategy. For each question, you pick an answer, write your own, or ask Grove to help you explore the options.
3. Shape the plan with Grove
Grove writes the plan with you, and you can edit every word. First comes the problem and the solution, in a document called Opportunity and Solution. Then Grove splits the work into projects, in a document called Scope. Each project is a slice of work that can ship on its own. Most projects have 1 to 3 outcomes: things a user can do once the project ships.
4. Settle the details
For each project, Grove works through the Requirements with you, one decision at a time. Requirements hold the decisions a coding agent can't make on its own.
5. Hand it off to be built
When a project is ready to build, a builder picks it up in their coding agent with the Grove command-line tool. If something in the plan is unclear, the question comes back to you as a thread instead of a guess.
6. Check what shipped
When a pull request linked to a project merges, Grove reads the code. Next to each outcome, Grove shows whether the work looks done. You make the final call, and tick the outcome done. This step needs GitHub connected to your workspace.
What you'll find in Grove
Workspace. Your team's home in Grove. Everyone in the workspace sees the same work.
Initiative. A theme of work, like a feature effort. It holds the plan and the projects.
Project. A slice of work, specified clearly enough for developers and their coding agents to build. Each project has an ID, such as P-003.
Outcome. Something a user can do once a project ships.
Thread. A conversation about an initiative, a project, or a passage in a document. A thread stays open until someone closes it.
Session. A chat with Grove.
For the full list, see Key terms.
Who uses Grove
Product leads decide what to build and why. The product lead is whoever owns the outcome: a product manager, a designer, a founder, or an engineering lead. Start with Quick start for product leads.
Builders turn projects into working software with their coding agents. When the plan isn't clear, they ask instead of guessing. Start with Quick start for builders.
Grove asks questions, researches, drafts the documents, and keeps track of each decision. You make the decisions. Grove makes sure they get made, written down, and carried forward.
Next steps
How work moves through Grove, from idea to shipped
Find your way around: Queue, Work, and Strategy
Our product principles