Can you code? Can you illustrate? Can you build? Piece by piece, you sketch, implement, hone, finetune, improve, retry, go into detail, expand... The ease of the process is relative to the tools adopted.
Of course there has to be knowledge behind it. Of course you have to know your tools. But "wild horse" and "diligent consultant", axe and scalpel require different degrees areas and modalities of competence.
A well built tool will build on the competences already natural for the professional (e.g. a graphic designer will be able to sketch and to instruct the machine in a reasonably standard language). Of course the better you know your tool, the greater the effectiveness. But currently, the systems can be strongly unreliable - they do not respect the request.
The user will have to learn to deal with a machine taking natural language as an input just like any manager has to know how to speak to personnel to obtain what is wanted. On the other hand, the implementation of "virtual personnel" which is reliable is a responsibility of the tool developers.
It seems like you agree based on parts of your comment like "A well built tool will build on the competences already natural for the professional".
I believe there will always be some amount of navigation of the latent space required, and people who don’t understand how to navigate it will struggle.
To use your analogy, even if the horse is tame you still need to know how to ride it.