obra/superpowers@using-git-worktrees

Isolated git worktrees can be created instantly by selecting a deterministic project-local directory, verifying .gitignore status, creating a new branch worktree, and bootstrapping dependencies. This prevents feature work from polluting the main workspace during parallel branch development.

Managing multiple git branches safely requires creating isolated worktrees in project-local directories that are verified against .gitignore rules. If a directory is not ignored, the system adds the ignore entry and commits the change before creating the worktree.

Bootstrapping project dependencies after creating a git worktree involves automatically running project-specific setup commands like npm install, cargo build, pip/poetry install, or go mod download, followed by executing test commands to validate a clean baseline.

Git worktrees are fully applicable to supervisor-driven subagent workflows that require separated, reproducible workspaces. Each subagent can operate in an isolated worktree with its own branch, dependencies, and clean test baseline without interfering with other tasks.

Git worktree creation respects CLAUDE.md preferences during directory selection. The system prefers a .worktrees directory, falls back to a worktrees directory, honors CLAUDE.md configuration, or prompts the user when the location is ambiguous.

Git worktree setup checks that project-local directories are gitignored to prevent repository contamination. If the directory is not ignored, the system automatically adds the ignore entry and commits the change before proceeding with worktree creation.