> it also has no reason to exist.
I despised having to produce design documents for software projects 20 years ago (the last time I had to do it as a software engineer). I wanted to jump straight to coding. I begrudgingly found that, much like research papers, it's a forcing function in really understanding the problem space.
Over the last year, I've found that, at least for nontrivial things, if my agent makes a terse (under 300 line) technical design doc that describes their research and their tasks, it can highlight any disconnects between what I asked and the agent's interpretation. It also serves as context to ramp up cross-model reviews, and as historical reference material when I have to Chesterson's fence something later. I wrote up more about this here: https://photostructure.com/coding/claude-code-tpp/
I know a lot of engineers who hate writing design docs. I think of them as being more comfortable with ideas in code than with English. And there are good reasons for that. But ideas in code are trapped, whereas ideas in English are portable and potentially viral in how they move between people.
But all those English-hating engineers now produce shitty AI design docs, which tick a box but have less than zero influence on anyone else’s thinking.