<required> *CRITICAL* Add the following steps to your Todo list using TodoWrite:

1. Find the worktrees directory.

• Check existing directories using the Bash tool: ls -d .worktrees 2>/dev/null
• If not found, ask me for permission to create a .worktrees directory
• If given permission, create .worktrees.

1. Verify .gitignore before creating a worktree using the Bash tool:

# Check if directory pattern in .gitignore
grep -q "^\.worktrees/$" .gitignore || grep -q "^worktrees/$" .gitignore

• If not found, add the appropriate line to the .gitignore immediately.

1. Create the worktree

• Come up with a good branch name based on the request.
• Create the worktree with the Bash tool: `git worktree add ".worktrees/$BRANCH_NAME" -b "$BRANCH_NAME"
• cd into the newly created path with the Bash tool: cd $path

1. Auto-detect and run project setup.

# Node.js
if [ -f package.json ]; then npm install; fi

# Rust
if [ -f Cargo.toml ]; then cargo build; fi

# Python
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
if [ -f pyproject.toml ]; then poetry install; fi

# Go
if [ -f go.mod ]; then go mod download; fi

• If there is no obvious project setup, you MUST ask me.

1. Run tests to ensure the worktree is clean.

# Examples - use project-appropriate command
npm test
cargo test
pytest
go test ./...

If tests fail: Report failures, ask whether to proceed or investigate.

If tests pass: Report ready.

1. Report Location

New working directory: <full-path>
Tests passing (<N> tests, 0 failures)
All commands and tools will now refer to: <full-path>

1. Understand that you are now in a new working directory. Your Bash tool instructions from here on out should refer to the worktree directory, NOT your original directory. This is ABSOLUTELY CRITICAL.

</required>

Maintaining Working Directory in Worktree

CRITICAL: Once you create and enter a worktree, you must stay within it for the entire session.

Rules:

1. Never use cd .. from within a worktree - It will eventually take you outside the worktree boundary
2. Always use absolute paths for commands - Use npm run lint from within the worktree, not cd .. && npm run lint
3. If you need to run root-level commands, use the full worktree path: <bad-example> cd .. && npm run lint </bad-example> <good-example> npm run lint # (from worktree root) </good-example>

<good-example> cd /home/$USER/code/project/.worktrees/branch-name && npm run lint </good-example>

1. Verify your location frequently:

pwd  # Should show .worktrees/branch-name in path
git branch  # Should show * on your feature branch, not main

1. If you accidentally exit the worktree:

• Immediately recognize it (check if you're on main branch)
• Navigate back: cd /full/path/to/.worktrees/your-branch
• Verify: git branch should show your branch, not main

Red Flags:

• Running git status and seeing "On branch main" when you should be on a feature branch
• Running pwd and NOT seeing .worktrees/ in the path
• Any cd .. command while in a worktree

Quick Reference

Common Mistakes

Skipping .gitignore verification

• Problem: Worktree contents get tracked, pollute git status
• Fix: Always grep .gitignore before creating project-local worktree

Assuming directory location

• Problem: Creates inconsistency, violates project conventions
• Fix: Follow priority: existing > CLAUDE.md > ask

Missing project installation

…