The useful detail is often in your head
You know why the task matters, what the customer asked and what went wrong last time. When typing feels laborious, it is tempting to leave that background out.
Nathan’s habit is to explain the job aloud. He can include a reason, remember an example and correct himself as he goes. The conversation does not need to sound like a technical specification.
Give it four things
Explain what you want, who it is for, what you already have and how you will recognise a good result. If a detail is missing, ask it to interview you.
Use dictation if that is comfortable, or type. Check transcribed names, numbers and addresses before relying on them. The purpose is to communicate the job clearly in the way that works for you.
Keep talking when you see the first attempt
A preview gives you something concrete to react to. Say which part is confusing or what needs to change. Then try the revised result.
The calculator exercise in You Don’t Need to Know How follows this pattern. Try it yourself.