Get Started
Build with Claude Code

Mission 7 of 7

Capstone: ship a real feature from issue to deployed PR, and time it.

Six missions of technique become one afternoon of doing it for real. You'll take a feature your users asked for through to a merged pull request, then fix the process for next time.

90 minAdvancedFree (uses your existing Claude Code setup)Step 1 free

What you'll do

Pick a feature and run one prompt

Choose an issue, start the timer, and paste a single kickoff prompt that runs the whole process with gates for your judgement.

Plan, build and test it

Review the plan, approve each step's diff, then exercise the feature in the browser and open the pull request.

Merge, time it and hold a retro

Deploy, write down your numbers, then turn what went wrong into one new CLAUDE.md rule.

  • A PR description that answers the reviewer's questions first
  • A real number for how long a feature takes you now
Before you start
  • All six earlier missions done, so CLAUDE.md, hooks, the browser MCP and the reviewer agent exist
  • A real feature request in your issue tracker. Medium: a few files, maybe a data change, some UI. Not a one-liner, not a rewrite
  • A deploy pipeline that gives you a preview URL per PR (Vercel, Netlify, Cloudflare Pages, Render all do). If you don't have one, the Launch a SaaS track sets it up
  • A timer. Phone is fine
Your progress0/7
01/07Pick the feature and start the clock0 done
STEP 01 of 07~8 min

Pick the feature and start the clock

The right size of feature is the one that would have taken you a day. Not an hour, not a week.

Everything here depends on choosing a feature of the right size, and a day's work is the target.

Choose the feature

Open your issue tracker and find a feature that fits these three tests.

  • Users have asked for it, so finishing it matters.
  • You can picture the whole thing but not the whole diff, so it needs the process.
  • It touches at least two layers (data and UI, or API and email), so there's something to integrate.

If you're between projects, use the team accounts feature from the plan mode mission on the invoicing app, or any feature in a side project you've been putting off.

Get ready and start the clock

  1. Make sure the tree is clean (git status), you're on main and up to date, and the dev server runs.

  2. Then start a timer and write down the time. You'll want this number.

    Tip
    Create a branch now: git checkout -b feat/issue-[n]. Everything commits to this. If it goes badly you delete one branch.
Checkpoint
Issue chosen, branch created, tree clean, timer running. Now you hand it the whole process in one go.
Stuck? Ask the community
Next mission · The faceless reel systemPick a lane that can actually hit a million views
→