Seven phases. Seven shipped artifacts. A mastery gate for each one.
A free, self-paced curriculum that takes you from "I use LLMs" to "I can design, evaluate, and ship production agents on the LangChain / LangGraph / LangSmith stack — and deliver them as a service."
The ecosystem moves fast, so it optimizes for durable skills — agent architecture, evaluation, observability, productionization — over memorizing today's API surface. Two things make it different from the many agent tutorials out there.
| Week | Phase | Deliverable you ship | Hours |
|---|---|---|---|
| 1 | 0 — Foundations | Traced hello-world (tool call + structured output) | ~8 |
| 2 | 1 — First agent | One agent, 3 real tools, one nested trace | ~8 |
| 3 | 2 — LangGraph | Rebuilt agent: persistence + approval interrupt | ~10 |
| 4 | 3 — RAG, memory, MCP | Agent with knowledge base + long-term memory + MCP tool | ~10 |
| 5 | 4 — Evals & observability | Eval suite + CI regression gate + monitoring | ~10 |
| 6–7 | 5 — Production & deploy | Hardened agent on k8s (or LangSmith Deployment) | ~12 |
| 7–8 | 6 — Capstone + FDE drills | Capstone + case study + demo video + drill artifacts | ~12 |
The non-negotiable spine is 1 → 2 → 4 → 5 → capstone: build an agent, make it stateful, prove it works, ship it. Phase 3 isn't skipped — it's the one phase whose depth flexes when you fall behind.
k, reject an approval — friction should be conceptual, not syntactic.Not for you if you've never written Python, or you want ML research and model training — this is the applied agent-engineering layer.
# install uv + Ollama first, then from the repo root ollama pull llama3.1 # any tool-calling model works uv sync # create the venv + install dependencies cp .env.example .env # then set your Ollama + LangSmith values uv run python -m phase0.hello_agent # run the Phase 0 starter uv run pytest # run the offline tests
Then open phase0/README.md and start the loop: run → modify → ship → gate.
About $0 on the default path. Models run on local Ollama — if your machine is weak, a hosted provider works with a one-line .env change for a few dollars. LangSmith's free Developer tier covers the tracing, datasets and evaluations. Phase 5's DIY path runs on a local kind/minikube cluster, so no cloud bill; the managed path needs a paid plan and is presented as the client-engagement option, not a learning requirement.
A build check (definition-of-done as checkboxes), a closed-book concept check with answers hidden behind collapsible blocks, and an FDE scenario. Write your answer down before peeking — generating the answer first is retrieval practice, the single best-supported technique in the learning literature, and it only works if you don't read ahead.
Retrieval practice and spacing are the only two techniques rated "high utility" in the canonical review of learning techniques, and mastery gates raise outcomes roughly half a standard deviation across 108 controlled studies. The README cites the papers if you want them.
A deployed, evaluated, monitored capstone agent, plus a case study and a demo video — a portfolio that answers the question every FDE interview and client call comes down to: "How do you know it works?"
Yes. This repository's code and documentation are MIT-licensed. See the LICENSE.