Forge worktrees give a task its own isolated checkout so concurrent work never collides on HEAD or a shared branch. Use forge worktree, not raw git worktree add — the Forge command does the extra setup that a bare branch add skips.

Worktree lifecycle

When to use

• "Work on this in an isolated branch / worktree", "spin up a worktree for this".
• Parallel work: a second PR or issue you want to develop without disturbing the current checkout.
• "Clean up the merged worktrees" — reclaim worktrees whose branches already landed.
• Diagnosing "why did my new worktree miss its dependencies / node_modules".

This skill is the worktree lifecycle itself. The plan/ship stages may create a worktree as one internal step, but managing worktrees directly — create, list, remove, clean — is this skill.

Create

forge worktree create <slug>