Final capstone: ship a feature from plan to pull request

The steps

One step at a time. When a step’s check matches, tick it and the next one opens.

1. 01

   Step 1 of 5: Start in a worktree

   A separate checkout, so your main folder stays untouched.

   Add .claude/worktrees/ to .gitignore first. New worktrees start from your remote default branch, so they get the hook you pushed. A worktree is a fresh checkout: ask Claude to install dependencies.

   TerminalCopy

   Run: $ claude --worktree my-feature

   – What happens: Claude starts in .claude/worktrees/my-feature/, on a new branch worktree-my-feature.

   Check it worked

   In another terminal, git worktree list shows the new worktree.

   It worked — next step Not yet
2. 02

   Step 2 of 5: Plan the feature

   Nothing is edited until you approve.

   Start the prompt with /plan. Claude explores and writes a plan. Press Ctrl+G to edit it in your editor, then approve it.

   In Claude Code

   You type: › /plan add <your feature>. Done means <how we check it>. List the files you will change and the tests you will add.

   – What happens: Claude reads the code and writes a plan.

   Check it worked

   The plan names the files to change and the tests to add, and you approved it.

   It worked — next step Not yet Back
3. 03

   Step 3 of 5: Build with tests on every reply

   Your Stop hook checks each reply.

   Approving the plan switches Claude to editing. Each time it finishes a reply, the hook runs your tests.

   In order:

   1. Claude

      Claude implements the plan

   2. Hook

      Stop hook runs the tests

   • If a test fails

     Claude fixes it

     The failures go back to Claude

   • If all pass

     Claude reports back

   Check it worked

   Claude’s last reply ends with the tests passing, and /hooks lists the Stop hook.

   If it didn’t work

   /hooks shows no Stop hook.

   The hook isn’t on the remote default branch, which new worktrees start from. Push it and start a new worktree.

   It worked — next step Not yet Back
4. 04

   Step 4 of 5: Review before you commit

   `/code-review` checks the changes in a subagent.

   It reviews uncommitted changes in a background subagent with its own context. Ask Claude to fix the findings you agree with.

   In Claude Code

   You type: › /code-review

   – What happens: You can keep working while the review runs.

   Check it worked

   The findings arrive in your conversation, and the ones you accepted are fixed with the tests passing.

   It worked — next step Not yet Back
5. 05

   Step 5 of 5: Commit and open the pull request

   Claude writes the message and opens the PR.

   In Claude Code

   You type: › commit with a descriptive message and open a PR

   – What happens: Claude commits, pushes the branch and uses gh to open the PR.

   Check it worked

   The PR is open on GitHub with a clear description, and claude --from-pr <number> finds this session later.

   It worked — finish Not yet Back