That's weird, I'm the opposite. Previously I would start coding immediately, because writing the code helps me figure out the what and the how, and because I'd end up with modular/reusable bits that will be helpful later anyway.
Now I sit on an idea for a long time, writing documentation/specs/requirements because I know that the code generation side of things is automated and effortlessly follows from exhaustive requirements.
I used to do this, but found scoping my agent usage down to smaller chunks got better results than trying to do it all from the get go. And looking back it makes sense - code is the most expressive form we have to tell the computer what to do, not English.
The size of the chunk varies heavily on what I’m doing ofc.
How to do that for a complex greenfield project? Do you scope out just one module and let the agent code only that, with the intention of reusing that module later in the full project?
Now I sit on an idea for a long time, writing documentation/specs/requirements because I know that the code generation side of things is automated and effortlessly follows from exhaustive requirements.