using-git-worktrees

To create an isolated Git worktree, you add a new branch to a separate directory using `git worktree add`, which preserves your main workspace and prevents accidental changes to active branches during feature development.

Using Git worktrees is the best way to manage multiple branches without context switching, as it allows you to maintain separate working directories for parallel development and testing on the same project simultaneously.

Git worktree isolation handles safety by checking gitignore rules to ensure worktree directories are ignored, and it selects locations using a priority system that prefers `.worktrees`, then `worktrees`, then configuration preferences.

Yes, after entering a new Git worktree, you can run project setup commands like `npm install` or `cargo build` to prepare the environment, ensuring a clean baseline is validated before feature work begins.

You do not need a global configuration, but if you prefer storing worktrees outside the project, the setup supports a global location at `~/.config/superpowers/worktrees` and will prompt you to ensure safe directory selection.

Git worktrees share the same repository history, avoiding the disk space and synchronization overhead of cloning, while providing a priority-based directory system and automated setup to rapidly isolate features safely.