Using Git worktrees

Overview

Create a worktree only when isolation materially reduces interference or branch risk. Worktrees are optional setup, not a default precondition for implementation.

When to Use

• Large features or refactors that should stay off the current workspace
• Work that needs a clean branch or separate dependency state
• Parallel efforts that would otherwise interfere with the current directory

When Not to Use

• Tiny edits or single-file changes that do not benefit from isolation
• Repositories where the current workspace is already the correct branch and state
• Parallelizable work whose write scopes can remain isolated without changing branch state

Minimal Workflow