I think the main reason people don't do something like this more often is that this turns you from a "coder" to a "manager". Your task now is to serialize the issue and to ask the right questions / keep everything moving along.
I don't particularly mind because I cre more about building something than doing my craft but I can totally see how this will be different for many people.
Here's the philosophical conundrum: Do we prioritize learning new things (improve craft) or create value (build stuff)? The first used to lead to the second, but not as much anymore.
Yeah that's exactly it. You have to build up the proper context first. Get all the documentation to be nice and coherent and it will happily write beautiful code.
I don't particularly mind because I cre more about building something than doing my craft but I can totally see how this will be different for many people.