managing-git-worktrees

Create parallel Git worktrees using the wt- prefix naming convention and place them at your project root. Each worktree lets you work on different branches simultaneously without switching contexts, enabling concurrent feature development across your team.

Avoid creating worktrees in parent repositories that contain submodules; instead, create worktrees within the submodule itself. This prevents conflicts and ensures submodule-aware operations function correctly across your parallel development workflow.

Create worktrees with wt- prefixed names at project root, use each for isolated feature work, then delete them after merging. Prune stale worktree references regularly and repair corrupted entries to maintain a clean, functional worktree environment.

Yes, replicate .env and .serena configuration files into each new worktree to ensure environment consistency. This replication satisfies technical requirements and prevents configuration drift across your parallel development instances.

Avoid worktrees if your project structure doesn't support multiple concurrent checkouts or if you lack coordination between team members (PO, Manager, Developer agents). Worktrees require intentional lifecycle management; neglecting pruning and repair can degrade repository health.