dev-worktree

1# Dev Worktree
2 
3Set up or resume the correct workspace before feature work. Keep this skill focused on repository context, worktree isolation, and dependency bootstrap. Do not perform requirements, design, planning, implementation, testing, or review work here.
4 
5## Phase Contract
6 
71. Propose the exact workspace plan before changing branch or worktree state.
82. Confirm the target branch/worktree with the user before switching contexts.
93. Use `feature-<name>` for branch and worktree names, where `<name>` is normalized kebab-case without the prefix.
104. Prefer a project-local worktree at `<project-root>/.worktrees/feature-<name>`.
115. Use no-worktree mode only when the user explicitly requests it.
126. Run all follow-up commands in the verified target context.
13 
14## Start Feature Workspace
15 
16Use for a new feature start.
17 
181. Normalize feature name to kebab-case `<name>`.
192. Determine the project root, the directory containing `.git`.
203. If the user explicitly requests no worktree:
21   - Continue in the current repository and branch.
22   - Call out that branch/workspace isolation is reduced.
23   - Skip to dependency bootstrap.
244. Otherwise use branch/worktree name `feature-<name>`.
255. Ensure `.worktrees` is listed in the project `.gitignore`; if not, add it.
266. If branch does not exist, run `git worktree add -b feature-<name> .worktrees/feature-<name>`.
277. If branch exists and the target worktree does not, run `git worktree add .worktrees/feature-<name> feature-<name>`.
28…