using-git-worktrees

You isolate feature work by creating an isolated development workspace, which protects your current branch from experiments. The skill detects existing isolation and uses git worktrees to keep feature work separate across tasks and harnesses.

The best way is to prefer native worktree tools to avoid harness interference, falling back to a standard git worktree with safe directory selection when native tooling is unavailable. This ensures isolated feature work across multiple branches.

Git worktree isolation guards against nested worktrees and submodules to prevent project-wide disruption. It also verifies safe directory selection and ignores project-local directories to maintain a secure isolated development environment.

You need a git worktree when starting feature work or experiments that must run in isolation across multiple tasks, branches, or harnesses. It automatically detects existing isolation and skips creation if already in an isolated worktree.

Feature work disrupts your current branch because changes directly impact the main working directory. Creating an isolated workspace using git worktrees enforces separation, protecting your active branch from subsequent feature tasks and harness interference.