1
 22. set up worktree for implementation:
 32a. read `hack/create_worktree.sh` and create a new worktree with the Linear branch name: `./hack/create_worktree.sh ENG-XXXX BRANCH_NAME`
 4
 53. determine required data:
 6
 7branch name
 8path to plan file (use relative path only)
 9launch prompt
10command to run
11
12**IMPORTANT PATH USAGE:**
13- The thoughts/ directory is synced between the main repo and worktrees
14- Always use ONLY the relative path starting with `thoughts/shared/...` without any directory prefix
15- Example: `thoughts/shared/plans/fix-mcp-keepalive-proper.md` (not the full absolute path)
16- This works because thoughts are synced and accessible from the worktree
17
183a. confirm with the user by sending a message to the Human
19
20```
21based on the input, I plan to create a worktree with the following details:
22
23worktree path: ~/wt/humanlayer/ENG-XXXX
24branch name: BRANCH_NAME
25path to plan file: $FILEPATH
26launch prompt:
27
28    /implement_plan at $FILEPATH and when you are done implementing and all tests pass, read ./claude/commands/commit.md and create a commit, then read ./claude/commands/describe_pr.md and create a PR, then add a comment to the Linear ticket with the PR link
29
30command to run:
31
32    humanlayer launch --model opus -w ~/wt/humanlayer/ENG-XXXX "/implement_plan at $FILEPATH and when you are done implementing and all tests pass, read ./claude/commands/commit.md and create a commit, then read ./claude/commands/describe_pr.md and create a PR, then add a comment to the Linear ticket with the PR link"
33```
34
35incorporate any user feedback then:
36
374. launch implementation session: `humanlayer launch --model opus -w ~/wt/humanlayer/ENG-XXXX "/implement_plan at $FILEPATH and when you are done implementing and all tests pass, read ./claude/commands/commit.md and create a commit, then read ./claude/commands/describe_pr.md and create a PR, then add a comment to the Linear ticket with the PR link"`