start-task

To set up an isolated git worktree, provide a kebab-case task name and run the script to initialize a new worktree aligned to origin/main along with a task.md template. This creates a clean, parallel workspace to prevent cross-task interference.

Git worktrees provide isolated task environments that prevent context switching and merge conflicts. Unlike standard branches, a new worktree creates a separate directory for your task, keeping the main repository clean while allowing parallel work.

Yes, creating a new worktree requires a git repository with an existing main branch. The script aligns the new isolated task environment to origin/main to ensure your bug fix starts from a clean, up-to-date baseline.

The task name must be in kebab-case format, such as feature-auth-login or bugfix-login-error. This naming convention is required to initialize the new git worktree and generate the corresponding task.md template successfully.

Yes, git worktrees prevent cross-task interference by creating isolated task work environments. By spinning up a new worktree aligned to origin/main for each feature or chore, you keep your main repository clean and avoid merge conflicts.

After running the script with a valid kebab-case task name, it generates a new git worktree branch aligned to origin/main and initializes a task.md template within that worktree to help you track your isolated work.