This list explains the words you'll see in Grove. Words in bold match the labels in the app.

Places in Grove

Workspace. Your team's home in Grove. Everyone in the workspace sees the same work.
Queue. Your starting page. It shows what needs your attention.
Work. Tables of every initiative and project in the workspace. You can filter, group, and sort them.
Strategy. Four documents your whole product shares: Target Personas, Product Vision, Product Strategy, and Competitive Landscape. Grove reads them when it plans new work.
Ask Grove. The chat with Grove, beside every page.

The work itself

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. A project can ship on its own.
Project ID. A project's permanent ID, such as P-003. It never changes, even when the project's name does. Builders use it to pick up the project and to link their code to it.
Outcome. Something a user can do once a project ships. Each outcome has a short bold name, such as "Move a visit." Most projects have 1 to 3 outcomes.
Status. Where an initiative or a project is on the path from idea to shipped: Unplanned, Planning, Ready to build, Building, or Built. Initiatives have no Ready to build status.
Priority. How urgent the work is: Urgent, High, Medium, or Low.
Target. The date you aim to finish by.

Overview. The home page of an initiative or a project. It shows its status, its people, its dates, and its projects or outcomes.
Plan. The section of the sidebar that holds the official plan documents.
Opportunity and Solution. The initiative's first document. It describes the business need, the users and their problems, and the solution.
Scope. The initiative's delivery plan. It lists the projects, in the order to build them, and what is out of scope.
Requirements. A project's detailed rules. They hold the decisions a coding agent can't make on its own. A question that is still open stays visible in the document until someone settles it.
Scratchpad. Working material that is not part of the official plan. It holds Documents, Visuals, and Decision guides.
Visual. A diagram or mockup that Grove draws. A visual can sit inside a document or stand on its own.
Decision guide. A side-by-side look at the options for one decision. Grove makes one when you choose Help me explore & decide.
Version history. Earlier versions of a document. You can compare versions and restore an older one.

Session. One chat with Grove. You can start a new session at any time, and come back to an old one later.
Thread. A conversation about an initiative, a project, a document, or a passage in a document. A thread stays open until someone closes it. A reply to a closed thread opens it again.
Waiting on you. Threads and sessions where someone needs your answer.
Lead. The person who owns the outcome of an initiative or a project.
Members. The people who build a project.
Archive. Takes an initiative or a project out of your workspace. Archiving an initiative also archives every project inside it. Only the Grove team can restore archived work.

Product lead. Whoever owns what a piece of work must achieve: a product manager, a designer, a founder, or an engineering lead.
Builder. A person who turns projects into working software, usually with a coding agent.
Coding agent. An AI tool that writes code, such as Claude Code or Cursor.
Grove CLI. Grove's command-line tool. Builders use it to pick up a project, read its plan, and ask questions from inside their coding agent.
Linked pull request. A pull request that names a project, such as "Part of P-003" in its description. Grove tracks linked pull requests on the project's Delivery tab.
Outcome tags. The tags next to each outcome that show how far the work has come: Nothing linked, Building, Ready for review, Needs you, and Done.