using-git-worktrees

Enforce a single Git checkout workflow to prevent parallel development conflicts by ensuring all project tasks occur serially in-place without creating additional worktrees.

A single-worktree workflow restricts all daily development, bug fixes, and experiments to one active checkout, ensuring serial progress and avoiding complicated merges.

Manage feature work by proceeding with repository tasks using only the current checkout, documenting changes in-place, and avoiding isolated worktrees to maintain serial progress.

No, enforcing single-checkout discipline requires no external tools beyond Git, validating that no additional worktrees exist and prompting for ownership when conflicts arise.

Strict single-worktree version control prevents misplaced changes by validating that no additional worktrees exist, forcing developers to work serially and avoid accidental switching.

When worktree conflicts arise during single-checkout development, the workflow provides clear ownership guidance to resolve the issue and ensures serial progress on tasks.