Using Git Worktrees

Purpose

Create isolated workspaces for implementation work without disturbing the main checkout.

Before Creating Anything

Check whether isolation already exists:

1. Are you already inside a worktree?
2. Are you already on a non-main branch?

If either is true, report that isolation already exists and skip worktree creation.

Directory Selection

Prefer these locations in order:

1. .worktrees/
2. worktrees/
3. create .worktrees/

Before creating a project-local worktree directory, verify it is gitignored. If it is not, fix that first.

Creation Flow

1. Determine the current branch and default branch.
2. Choose the base branch.
3. Create a new worktree with a descriptive branch name.
4. Run an initial project sanity check in the worktree.

Example commands:

git rev-parse --git-common-dir
git rev-parse --git-dir
git rev-parse --abbrev-ref HEAD
git worktree add .worktrees/<branch-name> -b <branch-name> <base-branch>
./gradlew build

Spectre Notes

• Keep .plans/ in the root checkout rather than inside the worktree.
• Use absolute paths when switching between Spectre and prior-art repos under ~/src.
• Prefer a worktree for implementation-heavy tasks, not for tiny doc-only edits.