The brief is the work
A fuzzy job still gets you a finished-looking draft. That draft is often the expensive part.
You ask an agent to fix the docs. Twenty minutes later you have a new README, a made-up stack, and a fake history of the project. The prose is clean. It sounds sure. You only wanted one command for contributors to run before a pull request.
The agent did not ignore you. It filled every blank you left. Vague instructions still count as instructions. The model keeps writing until the page feels long enough to count as work.
The polish pass is not your real job. The brief is.
Answer three questions before you send anything. What finished thing should exist, and who is it for? What must stay the same, and what must the agent never invent? How will you check success with yes or no, not with “it feels right”?
If you cannot answer those first, the agent will answer them for you. Then you spend the afternoon undoing a draft that already chose your meaning.
Write the brief first. That is the work.
One thing to send an agent
Before you write anything else, answer these and wait for my OK: 1) What finished thing are you making, and who is it for? One sentence. 2) What must not change, and what must you not invent? 3) Give me three yes/no checks I can use to see if you are done. Do not start the real deliverable until I approve.