Write a decision log entry that's actually useful in 6 months
Most decisions are recorded with too little context to be useful later. This template forces enough specifics to reconstruct the decision rationale a year later.
Write a decision log entry for: {{DECISION}}
Raw context:
{{CONTEXT}}
Structure:
- Date and decision-maker.
- Decision in one sentence.
- The 2-3 alternatives we considered and why we passed.
- The single most important constraint that drove the choice.
- The assumptions we're betting on (if any one of these turns out wrong, the decision was wrong).
- The trigger condition for revisiting ("if X happens, reopen this decision").
- Owner and review date.
No platitudes. If we don't know the assumptions or trigger, write "unknown — flag for follow-up." {{DECISION}}{{CONTEXT}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{DECISION}}{{CONTEXT}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.