Earlier quoted context omitted.
One can reason by analogy here. In a pre-LLM world, a classic software team would have PMs, designers, and engineers. Of those three, the PM wouldn't have any real role in writing code. And they would rarely contribute a ton to the design. What they would be contributing is ideas, market insights, coordination, prioritization, etc. When the product ships, one would expect the PM to feel a real sense of accomplishment…
It's more akin to someone commissioning a piece of art, where they describe the piece in varying detail and then it's the responsibility of the artist to see it through, perhaps deciphering ambiguities in the p̴r̴o̴m̴p̴t̴ commission brief. If you want to stick with the PM analogy, it would be akin to the manager spending 30 minutes writing up a draft spec, passing it off to their employees and then spending the rest…
But I think most of this stuff is iterative, multi-turn. You type a thing in, see what comes back, and then repeat until you have something that satisfies your desire.
Taking the manager analogy. If you spent 30-minutes writing up a draft spec, waited for the outputs, had a review meeting where you provided good feedback, and then repeated that cycle until the product was done... Again, I think that manager (assuming, of course, that their feedback was useful) should feel some pride in shaping that output!