That was totally upended by agile, that emphasized that yes, a clear, unambiguous specification is needed, and the best language for that is a programming language. Don't waste time writing a detailed spec in English, get right to writing it in code that you can execute and get immediate feedback on.
Now people want LLMs to write the code for them, so they are back to saying we just need to give the LLMs clear enough direction, a clear specification. It's amazing to witness history not exactly repeat itself, but very clearly rhyming
I don't particularly think "y7u8888888ftrg34BC" would pass as a crystal clear requirement at my workplace :<
Do you mean something different?
Last I checked, specs improved output quality. There are hiccups with complex, difficult specs but I guess that much is obvious.
This is more information than the average users gives you when requesting new features.