01What this module is about
Starting a project with AI is easy. Finishing one is where most people struggle. There's always one more tweak, one more version, one more "while we're at it".
You already decided what "finished" means, back in Module 3. This module uses that to call the project done, with a final check you can trust. Then it shows you how to keep it from going stale, and how to make your next project start better than this one did.
By the end, your project will be finished, checked against your plan, and backed up. You'll also have a short list of lessons for next time.
Not finished the whole project yet? That's fine. Run this module on the part you have finished, such as your first newsletter or your first chapter. Check it against the lines in Finished when that apply to that part. Then come back and run it again when the rest is done.
02How you know it's finished
Open your project plan, PRD.md, and find Finished when. That list is your finish line. Not "perfect". Not "as good as it could ever be". Just: is every line on that list true?
For each line there are only two good outcomes:
- Done. It's true, and you can show it.
- Moved to next time. You've decided, on purpose, that it can wait. It goes on a list for the next version.
What you shouldn't have is a line you're quietly ignoring.
03Text to copy
The final review. Start a fresh chat inside your project, or use a different company's tool for a second opinion. A different tool can't see your project, so paste in PRD.md first. Then paste this, along with your finished work:
Read PRD.md. Go through every line under Must do, Must not do and Finished when. For each line, say Met, Not met, or Can't tell, and show the evidence from the work. Then list anything still under Open questions. Only report problems that affect whether the project is finished. Skip style.
Lessons learned. In the same chat, paste this:
Looking back at this project, list up to five lessons for next time. For each one, write the line I should add to my Instructions or Reference file so it doesn't happen again. My problems list and my checklist are below. [paste your problems list and CHECKLIST.md]
04Your steps
Step 1: Run the final review
Paste the final review prompt, with your work. Read each Met, Not met and Can't tell. For each Can't tell, check it yourself.
Step 2: Close the gaps or move them
For each Not met, decide. Either fix it now, using the build-and-check loop from Module 6, or move it to a list called Next time at the bottom of your PRD. Then run the review again until everything is Met or moved.
Step 3: Keep the lessons
Run the lessons prompt. Save the answer as LESSONS.md in your project folder. Then copy the useful lines into your Instructions or Reference file, and update your tool, as in Module 1.
Your three files are now better than when you started. For your next project, start from a copy of them, not from blank. That's how each project begins better than the last.
Step 4: Wrap it up
- Save the final version with a clear name, like newsletter-final.md.
- Back up the whole project folder, as in Module 8.
- In CONTEXT.md, change "Working on now" to say the project is finished, with the date.
- Clear out HANDOVER.md, or write one last note saying where everything is.
05Keeping it from going stale
A finished project can still go out of date. The facts change, the tools change, and the AI changes. Ten minutes a month keeps it healthy:
- Read CONTEXT.md and REFERENCE.md. Update anything that has changed.
- Run your test task from Module 5 when your tool announces a new model. If the answer gets worse, you'll know before it matters.
- Check your tool's memory and privacy settings, as in Modules 4 and 8. Delete anything wrong.
- Look at your Next time list. When it's long enough, it's the start of version 2. Write a new PRD for it, and begin again at Module 6.
06Common problems
- It never feels finished. Go back to your Finished when list. If every line is met, it's finished, even if you can think of improvements. Put those on Next time.
- The review finds lots of small things. Fix what affects whether it's finished. Skip the rest, as in Module 6.
- The project grew beyond the plan. That's normal. Either add the new parts to the PRD on purpose, or move them to Next time. Don't let them sit in between.
- You can't tell if a line is met. The line is too vague. Rewrite it so it can be checked, as you learned in Module 2.
07You've finished the course
Here's the whole method on one page. Use it for every project from now on.
- Set up your three files in a project, with the six starter lines. (Module 1)
- Ask with the four parts: what you want, what it should know, the limits, and what done looks like. (Module 2)
- Plan with a PRD before you build. (Module 3)
- Start fresh chats and carry your work with a handover note. (Module 4)
- Start with the default model and step up only when needed. Keep a test task for trying new tools. (Module 5)
- Build one small piece at a time, and check each with fresh eyes. (Module 6)
- Check the facts that matter yourself, every time, with your checklist. (Module 7)
- Stay safe. Keep secrets out, back up your folder, and approve anything that sends, spends or deletes. (Module 8)
- Let agents help with small, safe tasks, with a clear brief. (Module 9)
- Finish against your plan, keep the lessons, and start the next project from your improved files. (Module 10)
08Test
Answer yes or no about your project.
- Did a fresh chat review your work against every line of your PRD?
- Is every line under Finished when either met, or moved to Next time on purpose?
- Have you saved LESSONS.md, and copied at least one lesson into your Instructions or Reference file?
- Is the final version saved with a clear name, and the project folder backed up?
- Does CONTEXT.md say the project is finished, with the date?
Five yes answers: you pass, and you've finished the course. Well done. Pick your next project and start again at Module 1, from your improved files.
09Sources
Checked on 11 November 2026.
- Reviewing the finished work against your plan, line by line, and skipping style: Anthropic, "Best practices for Claude Code" (code.claude.com), under "Review against your spec".
- The finish line, Next time, lessons learned, starting from improved files, and the monthly check: our own advice.