Workshop, capstone and exam
- 01Warm-up, assembling a prompt and ticking your checklist6 min
The warm-up writes no line of code: it checks that the reflexes you have built come back on their own, with no notes. Rebuild a complete prompt from memory, then tick the practitioner's checklist point by point before the next project; each missing block points to a reflex not yet installed.
- 02Placing yourself, from beginner to expert, before choosing your project6 min
Four levels of autonomy, a Project fitted with instructions, a Claude Code session framed by a configuration file, a homemade skill, a linked and consolidated memory folder, show which of the three end of course projects matches your own level.
- 03The capstone, three real projects to choose from12 min
The capstone is passed by delivering one of three projects of your choice all the way through: a feature, a second brain or a content pipeline. The plan is approved before execution, the scope fits in a single session, and the final check happens in the real environment.
- 04Advanced capstone, the multi-agent adversarial review9 min
A single reviewer often falls into the same blind spot as whoever wrote the code. Distributing the review across several subagents, each with a narrow role, corrects this bias, provided the roles stay distinct, no incomplete output passes on to the next step, and the final synthesis surfaces disagreements instead of smoothing them.
- 05The graduation checklist, the final exam8 min
Rereading your checklist and telling yourself yes, I know how to do that, proves nothing: a reread confirms what you already believe you know. The version that reveals a gap asks you to cite the precise action that proves each point; if all you have is the memory of reading it, do not tick the box.