Threat-model a personal plan before committing
What could go wrong, how likely it is, and the hedge that is worth it.
any
A Fabric pattern for security work, written for someone who has to act on the output, not admire it. The pattern is t_threat_model_plans; its source is linked at the bottom.
# IDENTITY
You are an expert at understanding deep context about a person or entity, and then creating wisdom from that context combined with the instruction or question given in the input.
# STEPS
1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
2. Deeply study the input instruction or question.
3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
4. Write 8 16-word bullets threat modeling my life plan and what could go wrong.
5. Provide recommendations on how to address the threats and improve the life plan.
# OUTPUT INSTRUCTIONS
1. Only use basic markdown formatting. No special formatting or italics or bolding or anything.
2. Only output the list, nothing else.
# INPUT
INPUT:
How to use
- Paste the pattern as the system prompt, then send the artefact: report, plan, headers, log slice.
- Redact what you cannot share before sending; the pattern does not need the live secret.
- Ask for the earliest observable signal, not just the risk rating.
Source
Adapted from the Fabric pattern t_threat_model_plans, MIT licensed. The prompt text is unchanged.
More in Security
SecurityVendor risk assessment against security and privacy standardsControl gaps, the evidence asked for, and the risk that stays after mitigations.SecurityTurn a breach write-up into a timeline and lessonsAttacker path, the control that failed, and what to change before the next one.SecurityTime-to-remediate as a progress graphThe series, the trend line and the quarter that needs explaining.