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.
Anchor to one reader
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.
- Compare two outputs instead of trusting one
- Have the model flag what it could not cover
- Name the audience and the single goal before you generate
Cut before you polish
Write down what you never want as explicitly as what you do. The exclusions often do more work than the instructions.
- Ask for three angles, then cut to the one worth shipping
- Lower the reading level, then check what broke
- Compare two outputs instead of trusting one
Keep a negative list
Treat the first output as a draft, not a verdict. The prompt does the typing; you keep the judgment about what ships.
- Have the model flag what it could not cover
- Ask for three angles, then cut to the one worth shipping
- Save the prompt that worked so the next person reuses it
Ask for the reasoning, then the result. When the model shows its steps you can see exactly where to push back.