Skip to content

Schedule & day map ​

The day runs as an ordered sequence of nine hands-on parts (30–45 minutes each), with a lunch break in the middle and short breaks between blocks. We follow the sequence rather than fixed clock times, so the day stays on track even if a part runs a little long or short.

Day map ​

BlockWhat's in it
Block IParts 1–3
Lunch breakCatch up to a baseline if needed
Block IIParts 4–6
Coffee breakShort reset
Block IIIParts 7–9

Food during breaks and drinks throughout the day are available for everyone.

Part-by-part ​

PartSegmentApprox.What you'll do
1Framing & first agent~45 minMeet the scenario; run your first agent.
2Context engineering~35 minDecide what the model should and shouldn't see; build a context map.
3Memory~35 minBuild a middleware layer that automatically stores the active order in session memory.
Lunch1 hCatch up to a baseline if needed.
4Writing useful specs & personas~35 minSpecify functional requirements, memory requirements, and bounded personas with Spec Kit.
5MCP fundamentals~35 minFork and run the package manager app; map its capabilities to MCP resources, prompts, and tools.
6Build the MCP server~30 minBuild a small MCP server with typed tools, a prompt, and a resource.
Coffee break30 min—
7Agent Framework & first MCP-connected agent~45 minBuild a first agent that uses the MCP server.
8Native tools & A2A handoff~30 minAdd a native function tool, compare it with MCP, then define an Agent-to-Agent handoff.
9Human-in-the-loop & condition checker~30 minPause for human review of a suggested package-condition change; review the day.
Close—Wrap-up and next steps.

Finished a part early?

Extra depth for several parts lives on the Extra exercises page, including "apply it to your own solution" prompts based on the De LeesLantaarn case.