Grove has opinions about how product work should be run. They come from years of shipping software, and they shape everything Grove does: the questions it asks, the documents it writes, and when it asks you for something.
You don't have to agree with all of them. Grove tells you what it thinks, then follows your decision. But knowing these ideas helps you understand why Grove works the way it does.
Why we built Grove
Only the code got faster. AI made building fast. Deciding what to build, and checking what got built, are still slow. See Only the code got faster.
Who decides
The product lead decides. Grove challenges your thinking. You make the call. See The product lead decides.
Product owns the why and what. Builders own the how. See Product owns the why and what. Engineering owns the how.
How to plan
Start with the problem. Know who you're helping, and why, before you choose a solution. See Start with the problem.
Split big work into small projects. Each project ships value on its own. See Split big work into small projects.
Give each project 1 to 3 outcomes. If a project needs more than 4, split it. See Give each project 1 to 3 outcomes.
Write outcomes anyone can check. See Write outcomes anyone can check.
Requirements hold only what a coding agent can't decide. See Requirements hold only what a coding agent can't decide.
How to build and ship
A question beats a guess. When the plan is unclear, ask. See A question beats a guess.
Shipped isn't done until someone checks. Only a person marks work done. See Shipped isn't done until someone checks.
Pull people in only when it matters. See Pull people in only when it matters.