// Track

Documentation is King

Docs Are the Agent Interface

In agent-driven development, documentation stopped being a chore and became the operating interface — agents read your docs at the start of every session, so doc quality now sets the ceiling on agent output. Master the full stack beyond the PRD: READMEs, agent context files, ADRs, runbooks, learning loops, contract docs, and the CI gates that keep them alive.

Recommended: Complete Spec-Driven Development: PRD → Ship first

10 lessons~85 min total

Lessons are shown in recommended order. Complete them in sequence for the best experience — or jump to any lesson.

Lesson 538·7 min read

Documentation is King: Docs Are the Agent Interface

Agents read the docs before touching a single line of code — and that one change turns the decades-old rot loop into a compounding quality engine.

Lesson 539·8 min read

The Documentation Stack: Seven Doc Types, Seven Jobs

One doc, one job — a doc doing two jobs fails both. Map the seven types in your stack and the failure mode each one produces when misused.

Lesson 540·8 min read

The README is the Front Door

The 60-second orientation test: a new engineer or coding agent should answer what/run/where/gotchas without asking anyone — and the key-files table is what makes it work for agents.

Lesson 541·9 min read

Agent Context Files: Operating Instructions for AI

CLAUDE.md and AGENTS.md are a new doc type — persistent operating instructions a coding agent loads every session. Every line costs tokens. Earn the line.

Lesson 542·8 min read

ADRs: Write Decisions Down Before They're Folklore

An undocumented decision doesn't disappear — it becomes folklore, and folklore costs engineer-weeks when re-litigated and agent-hours when re-refactored.

Lesson 543·9 min read

Runbooks: Docs That Execute Under Pressure

A runbook is written for the worst version of yourself — 3am, paged awake, adrenaline spiking — and every implicit assumption you leave out becomes a trap.

Lesson 544·9 min read

The Learning Loop: Lessons Files & Post-Mortems

A correction that isn't written down resets to zero every session — the only mechanism by which agent quality compounds instead of repeating is a rule the agent reads at session start.

Lesson 545·8 min read

Docs as Contracts: References That Don't Drift

Hand-written API docs drift the moment schema and doc evolve independently — generate from a single source or pin with drift tests.

Lesson 546·9 min read

Keeping Docs Alive: Freshness, Ownership & CI Gates

Docs rot because nothing enforces freshness at merge time — CI gates, ownership signals, and deletion discipline are the only defenses that work.

Lesson 547·10 min read

Capstone: The Self-Documenting Repository

A self-documenting repository lets a new agent orient, operate, respect history, improve, and trust interfaces with zero human hand-holding — assembling the full kit is this track's capstone.