AGENTS AT WORK · 04 A visual series

Handoff artifacts

A relay race where the baton is a document. Toggle the spec's quality and watch what happens at the next leg.

The problem this replaces

Coding straight from a one-line ticket

"fix the export bug" function fix() { // ??? which export // ??? which format // ??? whose data } ? ? ?

No design, no blueprint, no spec — just a sentence and a blank file. Every gap becomes a guess.

How it works

The next leg checks the baton, not just that one exists

BLUEPRINT spec SPEC MUST HAVE ✓ acceptance criteria ✓ affected files ✓ data contract ✓ edge cases named CODE
A spec missing any of these fields is malformed — the code leg won't start on a guess.

That's why "approve the plan" isn't a formality — it's the moment you're checking whether this exact baton is complete enough to build from.

See it in action

One race, six legs

design → blueprint → spec: filters, CSV, admin-only, edge cases → code → tests → PR

Every leg received a baton it could actually run with.

So what

The spec you approve is the contract the code is written against.