Write a risk mitigation plan for a project
Naming a risk and having a real plan for it if it happens are different levels of preparedness.
- Use it for
- Anyone planning a project who wants real risk mitigation, not just a list of things that could go wrong.
A risk list that just names what could go wrong (operational, technical, financial) is genuinely half the work — the part that actually protects the project is a concrete step for each risk, decided calmly in advance, rather than improvised under pressure if and when the risk materializes. This prompt requires a real mitigation step attached to each named risk, not just the naming.
When not to use this
For a low-stakes project where the cost of an unmitigated risk materializing is genuinely minor, this level of planning is more ceremony than the project needs.
Did this work?
Each identified risk has a concrete mitigation step, not just a named concern with no plan attached to it.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.