A good operations prompt isn't a magic trick. It's a checklist you don't have to remember, run by something that never gets bored.
Make the output reviewable
Ask for the reasoning, then the result. When the model shows its steps you can see exactly where to push back.
- Save the prompt that worked so the next person reuses it
- Name the audience and the single goal before you generate
- Have the model flag what it could not cover
Reuse the recipe
Write down what you never want as explicitly as what you do. The exclusions often do more work than the instructions.
Keep a negative list
Lock the parts that never change and leave one slot for the variable. Now every run shares a family resemblance instead of starting from scratch.
Ask for the reasoning, then the result. When the model shows its steps you can see exactly where to push back.