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 ​
| Block | What's in it |
|---|---|
| Block I | Parts 1–3 |
| Lunch break | Catch up to a baseline if needed |
| Block II | Parts 4–6 |
| Coffee break | Short reset |
| Block III | Parts 7–9 |
Food during breaks and drinks throughout the day are available for everyone.
Part-by-part ​
| Part | Segment | Approx. | What you'll do |
|---|---|---|---|
| 1 | Framing & first agent | ~45 min | Meet the scenario; run your first agent. |
| 2 | Context engineering | ~35 min | Decide what the model should and shouldn't see; build a context map. |
| 3 | Memory | ~35 min | Build a middleware layer that automatically stores the active order in session memory. |
| Lunch | 1 h | Catch up to a baseline if needed. | |
| 4 | Writing useful specs & personas | ~35 min | Specify functional requirements, memory requirements, and bounded personas with Spec Kit. |
| 5 | MCP fundamentals | ~35 min | Fork and run the package manager app; map its capabilities to MCP resources, prompts, and tools. |
| 6 | Build the MCP server | ~30 min | Build a small MCP server with typed tools, a prompt, and a resource. |
| Coffee break | 30 min | — | |
| 7 | Agent Framework & first MCP-connected agent | ~45 min | Build a first agent that uses the MCP server. |
| 8 | Native tools & A2A handoff | ~30 min | Add a native function tool, compare it with MCP, then define an Agent-to-Agent handoff. |
| 9 | Human-in-the-loop & condition checker | ~30 min | Pause 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.