PlaybookPrompts

Write a decision log entry that's actually useful in 6 months

Productivity & Planning decisionsADR

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.

Prompt
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."
Variables to fill in
  • {{DECISION}}
  • {{CONTEXT}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{DECISION}}{{CONTEXT}}.
  3. Paste it into one of the recommended tools below.
  4. 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.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

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.