If you're talking about the original vibe coding, sure.

But there are many ways to apply LLMs in the development flow.

Only specifying features broadly is like a product manager might is definitely highly luck dependent wrt how buggy it will turn out.

But understanding the feature and determining what needs to be done broadly, then ask the LLM to do so and verify after if the resulting change makes sense according to your mental model of the software is definitely not that.

Also, I disagree with your implied message. I frequently struggle to articulate solutions even if I know how they'd work

This should apply to art even more, because art is strongly supported by emotions - and people may know the feeling of the emotion (of the image), but not have an explicit framework for it yet

People are trying to use Vibe Engineering for when you know what needs to be done and how, but are using an LLM as a tool to write the code faster and more efficiently.

The OG definition of Vibe Coding is just playing a client who wants $thing, but doesn't need how to write a line of code.