jonnify / Agile Agent Workflow / A3 · The roadmap layer / A3.9 / A3.9.2 · The annotated sources

A3.9 · Glossary & references · dive 2

The annotated sources

Every vetted Source the course cites, each with an abstract and the modules that draw on it — one place to read deeper on any technique.

The sources are the canon; the abstracts say what each one gives the workflow. Pick a source on the right to read its abstract and who cites it; the section below flips the index — pick a module, see what it stands on. Every Source is a real external link.

The bibliography Module coverage On the Portal References

Read a source · its abstract and who cites it

The Pragmatic Programmer

Tracer bullets, the single source of truth, DRY, and design by contract — the pragmatic core the workflow is built on.

cited by A1 · A3 · A3.9

The Pragmatic Programmer (Hunt & Thomas): tracer bullets, the single source of truth, design by contract. Cited by 3 modules: A1, A3, A3.9.

The bibliography

Ten vetted sources, each a real external link. A source entry carries a title, an author, an abstract that says what the source gives the workflow, and the modules that cite it. The sources are the canon the course stands on — not decoration, but the set of ideas the framework was built to.

The Pragmatic Programmer — Hunt & Thomas

Tracer bullets, the single source of truth, DRY, and design by contract.

cited by A1 · A3 · A3.9

Extreme Programming Explained — Beck

Small batches, iterations, continuous feedback, and the inspect-and-adapt loop.

cited by A1 · A3 · A3.1 · A3.2

Specification by Example — Adzic

The spec as executable, shared truth; the four artifacts a rung is built from.

cited by A1.04 · A3.3 · A3.9.1

User Stories Applied — Cohn

The Connextra story form, value over tasks, and the value ladder.

cited by A2 · A3.9.1

Continuous Delivery — Humble & Farley

Keeping the system releasable at every increment; the roadmap as the delivery plan.

cited by A3 · A3.9 · A3.9.1

INVEST in Good Stories — Wake

The six tests of a good story: Independent, Negotiable, Valuable, Estimable, Small, Testable.

cited by A2

Gherkin reference — Cucumber

The Given/When/Then form of an acceptance criterion.

cited by A2 · A3.9.1

User-story template (Connextra) — Agile Alliance

"As a … I want … so that …" — the role-need-value shape of a story.

cited by A2

The llms.txt convention — llmstxt.org

A machine-readable map of a site or course for agents.

cited by A0 · A3.9

Building effective agents — Anthropic

The agent as an implementer of well-specified, decomposed work; the Author/Operator division.

cited by A0 · A1.03 · A3.9.1

Every Source above is a real, vetted external link, reused across the course so the same idea always points at the same reference.

Module coverage

Flip the index the other way: pick a module and see which sources it draws on. The decomposition modules stand on the story canon; the delivery modules on Continuous Delivery and Extreme Programming; the reference module on the pragmatic core.

Which sources a module stands on · pick a module

A1 · Why draws on 3 sources: The Pragmatic Programmer, Extreme Programming Explained, and Building effective agents — the case for thin, provable slices.

A bibliography is a two-way index — every source to the work that cites it, every module to the sources it stands on.

The sources on the Portal

The Portal's F6 web chapter is built straight off this canon. Its phoenix.roadmap.md is Continuous Delivery — releasable at every rung. Its master invariant is The Pragmatic Programmer — design by contract. Its rungs are a value ladder from User Stories Applied. Its acceptance is Given/When/Then from the Gherkin reference. The bibliography is the set of ideas the framework was built to.

# The F6 web chapter, read as a citation list:
#   phoenix.roadmap.md      → Continuous Delivery (releasable at every rung)
#   the master invariant    → The Pragmatic Programmer (design by contract)
#   the nine-rung ladder    → User Stories Applied (a value ladder)
#   the acceptance criteria → Gherkin (Given/When/Then)

# Open /elixir/phoenix to read the chapter the canon was built into.

the principle

A bibliography is a two-way index — every source to the work that cites it, every module to the sources it stands on.

on the Portal

The Portal's F6 chapter is built straight off this canon — Continuous Delivery for the roadmap, The Pragmatic Programmer for the invariant, User Stories Applied for the ladder.

The sources are the canon the framework was built to — every source a real link, every link to a real book or reference.

References

The primary sources for the bibliography itself, and the sibling reference dives.

Sources

Hunt & Thomas — The Pragmatic Programmer — the pragmatic core the workflow stands on.
Humble & Farley — Continuous Delivery — the delivery discipline the roadmap plans.
Adzic, G. — Specification by Example — the spec as shared, executable truth.
Anthropic — Building effective agents — the Author/Operator division of work.

Related in this course

A3.9 · Glossary & references — the module hub.
A3.9.1 · The glossary — the previous dive.
A3.9.3 · The idea→framework crosswalk — the next dive.
A1 · Why an Agile Agent Workflow — the case the canon argues.
F6 · The Portal on the web — the chapter the canon was built into.