using-grove

Workflow

Step 1: Verify Grove is initialized

test -f "$(git rev-parse --show-toplevel)/.grove/config.json"

.grove/config.json

grove:grove-init

Step 2: Verify grove CLI is installed

command -v grove

Step 3: Create workspace

grove create --branch <branch-name> --json

path

id

{
  "id": "abc1",
  "path": "/tmp/grove/myapp/abc1",
  "branch": "agent/fix-login",
  "created_at": "2026-02-17T10:20:00Z",
  "golden_copy": "/Users/chris/dev/myapp"
}

Step 4: Enter the workspace

cd <path-from-json>

Step 5: Verify baseline

go.mod

go test ./...

package.json

npm test

Cargo.toml

cargo test

build.gradle

build.gradle.kts

./gradlew test

pyproject.toml

requirements.txt

pytest

Makefile

make test

Step 6: Report ready

Grove workspace ready.
  Path:        <workspace-path>
  Branch:      <branch-name>
  Build state: warm (cloned from golden copy)

Quick Reference

grove create --branch <name> --json

grove list

grove destroy <id>

Common Mistakes

• Using plain

  git worktree

  — worktrees start with a cold build cache. Grove's CoW clone preserves warm build state, making the first build incremental rather than from scratch.
• Skipping

  --json

  flag — the JSON output is required to reliably extract the workspace path and ID for later use.
• Not verifying grove initialized —

  grove create

  will fail confusingly if

  .grove/

  is absent. Always check first.

Red Flags

• grove create

  errors about uncommitted changes on the golden copy — clean up or commit the golden copy first, or use

  --force

  if the changes are intentional.
• Tests fail at baseline — the golden copy's build state is stale. Run

  grove update

  on the golden copy before creating workspaces.

• grove

  command not found after install — check PATH; grove installs to

  $GOPATH/bin

  by default.

Integration

• Replaces:

  superpowers:using-git-worktrees

  — prefer this skill in any Grove project. Disable

  using-git-worktrees

  to avoid conflicts.
• Called by:

  superpowers:brainstorming

  (Phase 4),

  superpowers:subagent-driven-development

  ,

  superpowers:executing-plans

• Pairs with:

  grove:finishing-grove-workspace

  — use that skill when implementation is complete and the workspace is ready to clean up.