Schedule
English-first: 12 teaching weeks, then an assessment week. Weekly time estimates are published after a timed pilot. Work due in a week is due on Sunday at 23:59.
Each week's page lists that week's lecture materials.
| Week | Topic | First session (lecture) | Second session | Due |
|---|---|---|---|---|
| Week 1 | The internals of coding agents | Build a minimal agent live, then read a real agent's requests: system prompt, tool list, loop and stop. | Studio: capture and read your own session. | A1 |
| Week 2 | Advanced context engineering | Prompting, research–plan–implement workflows and spec-driven development; MCP and tool design for a model reader. | Studio or guest; contribution projects introduced. | A2; project proposal |
| Week 3 | Agent skills and the CLI | What a skill encodes; trigger tests and near misses; working from the command line. | Guest or studio. | A3 |
| Week 4 | Customizing your agent and repository | Instruction files, hooks as gates, subagent roles. | Guest or studio. | Contribution 1; project technical specification |
| Week 5 | Agent-ready codebases | Structure, documentation, tests and checks that let an agent work; scoring readiness. | Guest or studio. | A4 |
| Week 6 | Agentic code review | What model review catches, misses and invents; disposing of each finding. | CP1 (30 minutes, on paper), then guest or studio. | A5; CP1 |
| Week 7 | Tests that notice a fault | A surviving mutant is a gap in the tests; a property and its shrunk counterexample; an agent that weakens a test to pass it. | Studio on your project's tests. | Project alpha and task backlog |
| Week 8 | Security | Text as data or as authority; an inert local injection chain; scan, triage and reproduce. | Guest or studio. | Contribution 2 |
| Week 9 | Background agents | Asynchronous and parallel agents; issue-to-pull-request pipelines; what changes when nobody is watching. | Guest or studio. | Contribution 3 |
| Week 10 | Evaluating agents | Can the check fail, was the pass earned, is the denominator complete; pass@k on a small table; calibrating a model judge. | Studio: audit one instance. | A6 |
| Week 11 | Building an AI-native team | Portals, gateways, routing and cost; recovering from an incident and proving it with a regression. | CP2 (30 minutes, on paper), then guest or studio. | CP2 |
| Week 12 | The software factory and what comes next | Self-running pipelines as a claim to test; course review. | Defense walkthrough; studio. | Contribution 4; final project |
| Week 13 | Assessment week | Project expo. | Individual defenses. | — |