--- name: stdd-worktrees description: "Work in an isolated workspace without fighting the platform's native isolation. Use when: Starting implementation work that should not disturb the user's current checkout." --- # Isolated Workspaces ## Order of preference 1. **Reuse existing isolation.** If you are already in a linked worktree or a platform-managed sandbox, use it. Never nest worktrees. (Check: `git rev-parse --git-dir` differs from `--git-common-dir`, and you are not in a submodule.) 2. **Use the native worktree tool** if it honors the placement policy. Otherwise use Git directly unless required platform lifecycle handling would break; then explain the conflict and ask. 3. **Fall back to `git worktree add`** only when neither applies, branching from the repository's integration branch unless told otherwise. ## Placement policy - An explicit user or project placement rule wins. Otherwise the worktree goes to `/.worktrees/`. - Resolve the primary checkout from Git metadata (`git rev-parse --git-common-dir`, `git worktree list`), never from the current directory. A submodule or bare repository may have none; when no location is unambiguous, ask. - Working trees never go inside `.git` or beside the project by default. - Check `git worktree list` and the destination; never overwrite or silently reuse another task's directory or branch. Verify Git-ignore; if absent, add the rule before creation and report the repository edit. - Never automatically relocate or remove existing worktrees; cleanup needs explicit authorization and inspection for live work and unsaved changes. ## After creating - Run the project's dependency setup (install, build) so the workspace is self-sufficient. - Run `stdd doctor --readiness` before trusting any verification output — a missing install or unbuilt package produces phantom failures. - Untracked and gitignored files (env files, credentials, build output) are per checkout — a fresh worktree never has them. - Run the narrowest baseline verification before changing anything. If the baseline is already red, report it and ask before proceeding. ## Shared state warnings - The git stash stack is shared across all worktrees of one repository. Prefer a temporary WIP commit over stashing; if you must stash, tag the entry and apply (not pop) by its SHA. - Never `cd` out of your assigned worktree into the main checkout to "fix something quickly" — open work there belongs to someone else.