A strategy prompt should help you make a decision, not just generate polished analysis. The fastest way to improve these prompts is to define the decision, the criteria, and the output shape before you add any tone or perspective.
When to use this guide
Use this guide when you need a prompt for prioritization, planning, market analysis, launch decisions, or risk review. If the result needs to be actionable, not just interesting, this workflow helps.
1. Name the decision explicitly
Start with the exact decision the prompt is supporting.
Examples:
- Which of these three launch bets should we run next?
- Should we build, delay, or cut this request?
- Which channel deserves the next four weeks of effort?
If the prompt does not name the decision, the answer will usually stay too broad.
2. Give the model evaluation criteria
Decision-ready outputs need criteria. Without them, the model will improvise what “best” means.
Useful criteria might include:
- revenue potential
- implementation cost
- confidence level
- time to validate
- strategic fit
A good strategy prompt often asks the model to explain how each option scored against the criteria.
3. Require tradeoffs, not just conclusions
This is where many strategy prompts fail. They ask for a recommendation but not for the reasoning pressure behind it.
Ask for:
- strongest argument for each option
- biggest risk for each option
- what evidence is missing
- why the final recommendation wins anyway
This makes the answer easier to review and much harder to confuse with empty confidence.
4. Define the output structure
A reliable structure might be:
- Situation summary
- Options
- Evaluation against criteria
- Risks and unknowns
- Recommendation
- Suggested next action
That shape works well for prompts related to Trading Playbook Architect or other decision-heavy workflows because it keeps the output useful for later review.
5. Test with a weak scenario and a messy scenario
A good strategy prompt should work when the evidence is incomplete, not just when the answer is obvious. Test it on:
- a clear decision with solid inputs
- a noisy decision with missing information
If the prompt becomes overconfident on weak evidence, add stronger constraints around uncertainty.
6. Save the prompt with notes for reuse
Once the prompt is working, save it with a stable name, tags, and a note about the decision type it supports. That turns one-off planning help into a reusable asset.
Bad vs better example
Bad:
- Analyze these options and tell me what to do.
Better:
- Compare these options using implementation cost, time to validate, and strategic fit. Name the strongest argument for each option, the biggest risk, and any missing information. End with a recommendation plus one next action.
Review checklist
Before publishing a strategy prompt, check:
- Is the decision clear?
- Are the criteria visible?
- Does the prompt force tradeoffs into the output?
- Does it handle uncertainty without pretending it has certainty?
- Could another operator reuse it next week?
For adjacent vocabulary, read Strategy Prompt and Playbook Prompt. For the broader system view, see How Strategy Prompts Become Reusable Playbooks.