worktreelisted

# Worktree Spin up an isolated git worktree so a new feature, bugfix, or parallel agent run lives on its own branch and its own filesystem path — without disturbing your main checkout. Each worktree arrives ready to run: env files copied, a private port block assigned, install commands detected. Pairs naturally with `vd:cook` and `vd:fix` (implement in the worktree) and `vd:ship` (land it). ## What this skill is — and isn't | Skill | Question it answers | Output | |---|---|---| | **`vd:worktree`** | Where does this feature/branch live on disk, and how does it run without colliding? | Worktree + branch + env + ports, ready for work | | `vd:git` | How do I stage/commit/push *this branch*? | Conventional commits on the current branch | | `vd:ship` | Is this branch ready to land? | Tests → review → version → PR | | `vd:scout` / `vd:plan` | What am I going to build? | Reports + phase files | ## Standard location: `.worktrees/` All worktrees live at **`<git-root>/.worktrees/<repo>-<feature>/`** — one rule for every repo type: - **Standalone** → `<repo>/.worktrees/` - **Monorepo** → `<monorepo-root>/.worktrees/` - **Submodule** → topmost superproject's `.worktrees/` `.worktrees/` is a **top-level sibling of the `.work/` artifact umbrella**, deliberately not nested under it. Worktrees are full checkouts (heavy, contain source), so nesting them inside `.work/` would pollute artifact globs (`reports/`, `plans/`) and bloat the umbrella. The script auto-appends `/.worktrees/` and