Clear goals and house rules save more than anything else.
Do this
Why it helps
Name the place and the finish line
The assistant does not have to explore.
Ask for one change per goal
Small jobs are quick to review and quick to redo.
Say what not to touch
It keeps the assistant out of unrelated code.
Put standing rules in your company brief
You stop repeating them in every message.
Reject a step that is off track
Stopping early ends the spend early.
Ask for a plan before a big job
You can cut scope before work begins.
PromptA tight goal
Coder, on [repository], fix [one specific problem] in [file or area]. Do not change anything else. Run the related tests and open a pull request for review.
PromptPlan before spending
CEO, for [large goal], propose the smallest first step that gives me something I can review. Do not start until I agree.
PromptAsk what drove usage
CEO, which of my recent jobs used the most, and how could I have asked for them more tightly?