Notes from the team building Spectrace — engineering trade-offs, product missteps, design rationale, and stories from the customers using it.
Six months ago we asked a question that sounded silly: what if the spec wrote the tests? This is the story of what we found, what broke, and how a verdict bot ended up shipping faster than the IDE plugin we'd been planning for a year.
“The spec is the executable contract — everything else is a manifest of broken promises.”
What our beta customers actually do with the verdict — and what we got wrong about the UI on PR pages.
Requirements have two audiences: the future engineer and the AI. We redesigned the editor for both.
An AC clarifier that's good at edge cases is harder than it sounds. A bunch of small data choices mattered more than the model.
How a 24-person mobile team uses Spectrace to catch ambiguity before code review starts.
The hard part isn't the diff — it's connecting the change to what it was supposed to do.