Feature worktree workflow (Worktrunk)

The policy is in the always-loaded rule worktrunk.md (read it for approvals). This skill is the playbook. For wt flags, hooks, and config, the official worktrunk skill and wt <command> --help are the source of truth. Install hints per machine: the machine notes (~/.agents/rules/99-machine.md).

1. Decide: worktree or not

Use a worktree when the task is a feature, a bug fix, a refactor, or anything else that will be committed on its own branch and reviewed or merged.

Do not create one for: read-only work; small edits the user wants applied in place; a task whose branch and worktree already exist (resume it: wt list, then work in that path).

2. Start

command -v wt >/dev/null || echo "wt missing: fall back to plain git and tell the user"
wt list                                              # is there already a worktree for this task?
wt switch --create feat/<slug> --no-cd --format=json # branches from the default branch