using-git-worktrees

To create an isolated git worktree, the Skill detects if you are already in a linked worktree, then prefers native worktree tooling or falls back to manual git worktree creation to protect your current branch from edits.

A git worktree provides isolation for development by creating a separate working directory linked to your repository. You need it when executing plans or features to preserve a clean baseline and protect the main checkout.

After creating a git worktree, the Skill installs dependencies and runs baseline tests automatically. This verifies a clean project setup so you can begin feature implementation from a confirmed working state.

Yes, git worktree isolation works in submodules. The Skill verifies existing isolation first by checking whether you are already inside a linked worktree or submodule before attempting any new worktree creation.

Git worktree creation uses native worktree support when available, automatically falling back to manual git worktree creation only when needed. This ensures isolation setup works across different development environments.

Using a git worktree instead of branching directly protects your active repository checkout from unintended edits. It preserves a clean baseline for feature implementation and plan execution without risking changes to the main branch.