use-worktreeslisted

# Use Worktrees - Use the project's own worktree tooling where it exists: setup scripts, task runners, port allocation, seeded env files, devcontainers, or commands that run inside a container - Ask when the environment looks tooled but the entry point isn't findable - The steps below are the fallback for a project that brings nothing of its own ## Process 1. Ensure the branch you are creating the worktree from is up to date 2. Name the worktree exactly as the branch is named 3. Check the repo's `.worktreeinclude` (or equivalent list of env/config files the worktree requires to run) against what actually landed in the worktree, and manually `cp` missing requirements from the repo root 4. Let each worktree build its own dependencies e.g `vendor`/`node_modules` by running the real installation commands (`composer install`, `pnpm install`, etc.) inside it ## Handing a worktree back for review When the user wants to verify or review the changes made from a worktree: 1. Ensure the worktree has been committed to 2. Run `git checkout --detach` on the worktree before checking out the branch in the main repository directory ## Teardown - Prune "finished" worktrees as long as there are no pending changes