The big value is certainly in the less constrained stuff. Today I wanted to experiment with a hobby project, so I wrote a page of what I want to achieve. I then presented it to GPT4 as a "spec" and told it to act as a software architect and give me suggestions and ask for clarification. It gave me mostly good suggestions, asked a few good questions, and gave some feedback I disagreed with. I updated the spec to incorporate the good bits, clarified and firmed up the wording around the choices where it had made suggestions I disagreed with, and asked it to give another round of feedback. I turned around the draft 3 times, and it added value every time.
I could have done that with a person, but then I'd need someone who was available then and there that I wasn't taking away from other stuff.
To tie that to your points: This process was exactly an exercise in nailing down details that were missing because the short prose version was leaving huge gaps.
I intend to need a back and forth of filling in detail each step toward an implementation for that reason.
And I think this kind of tooling need to be built with that in mind: Write roughly what you need unless you already know how you want to express it in code. Ask for clarifications or a proposed plan. Iterate. Maybe with tooling giving examples of where it would head if prompted to fill in more detail.
I sure as hell won't trust it to just blindly do a task for me from a brief problem statement at this point.
Just as I wouldn't for most non-trivial tasks with most humans...