worktree-create

To create a git worktree for isolated feature development, use an automated command that sets up the worktree and initializes a tracking plan. This enforces input validation, detects the base branch, and creates the initial plan file automatically.

Yes, you can specify an explicit base branch when setting up a git worktree for parallel work. If the base branch is omitted, the tool automatically detects and defaults to either the main or master branch.

Using isolated git worktrees is the best way to manage multi-branch experiments without conflicts. This approach creates separate working directories for each branch, keeping parallel feature development completely separated.

Automatic plan initialization works with new git worktrees by creating a dedicated plan file under a specific active directory. This tracks progress and decisions linked directly to the newly created worktree for the feature.

No, you do not need to manually create a plan directory before creating a worktree. The automated workflow enforces input validation and handles the initial plan file creation under the active feature name directory automatically.

You should use isolated worktrees instead of standard git branching to maintain multiple working directories simultaneously. This allows parallel feature work and multi-branch experiments without stashing changes or switching branches repeatedly.