How treating code as a black box forced me to build a backlog that lives in git, per-ticket model dosing, and a review gate run by agents who know nothing about the code.
I'm a scrum master. I was a developer ten years ago. I have enough background to
discuss design and trade-offs with an LLM — but three months ago I made a
deliberate bet on my solo project: I would never read the code.
The specs define the tests. The tests control the code. The code is a black
box.
Coding agents imitate a healthy codebase well but bring no judgment to an empty one — so I built a spec-driven framework to…
Three years into my career, I raised my hand for a job that more senior engineers on the team had...
I spent months optimizing my AI development pipeline before realizing the bottleneck was never the pipeline. It was my specs.…
When I started having Claude Code build new web tools, I handed it abstract specs: design...
Spec-driven development hands AI the wrong job. The real win is arguing the design out in chat first, then letting the spec fall…
Spec-driven development is having a moment. Write a detailed spec, hand it to the agent, get working...
