Chapter 1 covered what you are talking to. Chapter 2 covered the room the work happens in. This chapter is the job itself: turning something you want into a change that exists, is checked, and can be picked up again tomorrow by a session that remembers nothing.

Most of the difficulty is on your side of the keyboard. Claude Code and Cursor will write the code either way. What decides whether the project finishes is how big a piece you hand them, what you said counts as done, and what you wrote down before the terminal closed.

Seven sections. Read them in order the first time.

  1. Outcome and boundary
  2. What fits in one go
  3. One bounded session
  4. Markdown files are the memory
  5. Folders a cold session can read
  6. Plausible is not proven
  7. Debugging without going in circles