Day 1 of 5: the spec
Day 1 of 5. The spec.
This week I'm walking through how we take a piece of work from idea to production with AI agents, one stage a day, the way we actually run it. Today is everything that happens before anyone writes code, human or agent.
We start by checking whether the thing already exists, whether we started it once and stopped, and how far it got. Agents will very happily rebuild something you already have, and do a nice job of it.
Then a short brief, and two lists before any code. Roughly this shape:
For: (the user, by role)
Job, in their words:
We'll know it worked when:
Not doing:
Must pass:
Must refuse:
If we can't fill in "must refuse", we don't understand the work yet.
Last week a brief asked a builder to add a lock so two requests couldn't overwrite the same record. The builder measured before writing anything. In real use the clash couldn't happen. The failures came from the test's own fake data colliding with itself, so we shipped a test that keeps it that way and no lock.
A model is very good at filling a gap with a confident guess. Most of the spec is us closing the gaps before it gets the chance.
Tomorrow, the code, and why the agent that plans the work never writes it.
When your team writes acceptance criteria, do you write down what the feature must refuse, or only what it must do?
