setup-worktrees

Automating git worktree creation for multiple tickets is handled by scaffolding a dedicated worktree per ticket off a CP branch. This organizes parallel development contexts under a local .worktrees directory and prevents cross-contamination between features.

Deterministic branch management creates per-ticket branches exclusively off the CP branch using hard-coded rules. It strictly prevents creating branches off main or master and reports clear outcomes if any git operation fails during the worktree setup.

Yes, git worktrees isolate parallel development by generating a separate working directory for each ticket. Keeping ticket branches off the CP branch and organized locally prevents cross-talk and cross-contamination during feature implementation.

The best way to structure worktrees for a feature plan is to scaffold them locally under a .worktrees directory. Running the setup process after planning automatically generates these worktrees off the CP branch for consistent organization.

Yes, the worktree setup process enforces branch hygiene by applying hard rules to never create branches off main or master. It ensures per-ticket branches are only created in a controlled manner off the CP branch.

Git worktree setup intentionally fails when branching off master because the process enforces hard rules against it. To maintain branch hygiene, per-ticket branches must be created off the CP branch instead of main or master.