isolated-worktreeslisted
Install: claude install-skill Zaheer-verse/deliberate-dev-claude
# Work in isolation
Each implementation task gets its own Git worktree and branch, including when one agent performs tasks sequentially. A branch alone, a subfolder, or a second agent in the same checkout is not isolation.
Inspect the repository root, existing worktrees, Git status and baseline commit. Keep the user's working changes intact. Do not stash, commit unrelated files, reset, force checkout, or clean as a shortcut. If the baseline contains uncommitted changes needed by the task, ask how to preserve/include them before proceeding; do not silently omit them. For a new project, establish an authorized initial Git baseline before task worktrees are created. If Git or worktrees cannot be used, report the blocker instead of substituting a shared directory.
Use [worktrees.py](../../scripts/worktrees.py) to prepare a validated dry-run plan:
```text
python <plugin-root>/scripts/worktrees.py create --repo <repo-root> --run-id <run-slug> --task-id <task-slug> --base <reviewed-base>
```
Quote actual absolute paths. Read [the CLI reference](../../docs/worktrees-cli.md) for accepted slugs and path rules. The default only prints a plan. Inspect its repo, branch, worktree and base_commit, then repeat with `--apply` under the existing authorization for local development. Record the returned absolute worktree, unique branch and pinned base revision in the run record.
The default destination is a sibling worktree directory; it must be writable. If the host sandbox permits only c