Work & projects · A4 portrait · v0.2.0
Decision One-Pager
A single-page decision memo: situation, complication, the decision required, an options table with pros/cons/cost, a highlighted recommendation, next steps and risks. For teams that decide on paper, not in meetings.
Paste the prompt into Claude (or any agent that can fetch URLs) with your content — you get back a finished, self-contained HTML file. Manifest ↗
Live preview — the example content ships with the template and is replaced by your content.
What an agent may change — and what content you should have ready. Everything outside these slots is fixed by design.
Slots
| Slot | Type | Req. | Example |
|---|---|---|---|
doc-title |
text | yes | Decision — CRM platform for the sales team |
title |
text | yes | Choose a CRM platform for the sales team |
owner |
text | yes | Bram Verlaan |
date |
date | yes | 13 Aug 2026 |
status |
text | yes | For decision |
situation |
html | yes | <p>The sales team tracks leads in a spreadsheet…</p> |
complication |
html | yes | <p>The team doubles by Q2 2027…</p> |
decision-required |
text | yes | Select and contract a CRM platform before 1 September 2026. |
recommendation |
html | yes | <p><strong>Choose HubSpot Starter.</strong> It fits the budget…</p> |
risks-content |
html | no | <p>Adoption risk — mitigate by…</p> |
footer-note |
text | no | Confidential — internal use |
Repeat: option (2–4×)
One row per option considered.
| Slot | Type | Req. | Example |
|---|---|---|---|
option-name |
text | yes | HubSpot |
option-summary |
text | yes | Starter CRM suite; marketing tools included. |
option-pros |
html | yes | <ul><li>Fastest onboarding</li></ul> |
option-cons |
html | yes | <ul><li>Costs rise at scale</li></ul> |
option-cost |
text | yes | €6.2k/yr at 14 seats; ~1 wk migration |
Repeat: step (2–6×)
One row per next step.
| Slot | Type | Req. | Example |
|---|---|---|---|
step-action |
text | yes | Start free-tier pilot with 3 reps |
step-owner |
text | yes | Sanne |
step-due |
text | yes | 20 Aug |
Optional blocks
risks— Key risks & mitigations panel at the bottom. Remove if the user provides none and none are evident.
The authoritative fill instructions from manifest.json — the only place a template may instruct an agent (why).
THIS MUST STAY ONE PAGE — that is the template's entire point. Limits: 2–4 options (remove data-example rows — they are preview content only), pros/cons max 3 short <li> each, situation and complication one paragraph each, 2–6 next steps. If the user's content overflows, tighten the wording — never shrink fonts or change CSS. Follow the pyramid principle: title states the decision (imperative, specific), decision-required is one sentence with a deadline or constraint, and the recommendation starts with the chosen option in <strong> followed by 2–3 sentences of rationale that reference the options table. Be honest in pros/cons — a table where the recommended option has no cons reads as spin. Every next step needs a named owner and a date. Keep the risks block only when real risks exist; write mitigations, not just worries. Use the user's language for content but keep section labels (Situation, Complication, …) as they are unless asked.
Published versions are immutable: /t/decision-one-pager@{version}/ never changes once live. /t/decision-one-pager/ always points at the latest.