{
  "spec": "quick-html/v0",
  "id": "decision-one-pager",
  "version": "0.1.0",
  "name": "Decision One-Pager",
  "description": "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.",
  "useWhen": [
    "decision memo",
    "one-pager",
    "options analysis",
    "recommendation doc",
    "beslisdocument",
    "proposal summary",
    "make the case"
  ],
  "category": "printable",
  "language": "en",
  "page": {
    "size": "A4",
    "orientation": "portrait"
  },
  "modules": [
    "edit-overlay",
    "print-helper"
  ],
  "slots": [
    {
      "name": "doc-title",
      "type": "text",
      "required": true,
      "example": "Decision — CRM platform for the sales team",
      "notes": "Browser tab title; used as the download filename."
    },
    {
      "name": "title",
      "type": "text",
      "required": true,
      "example": "Choose a CRM platform for the sales team",
      "notes": "Imperative and specific — the decision, not the topic."
    },
    {
      "name": "owner",
      "type": "text",
      "required": true,
      "example": "Bram Verlaan"
    },
    {
      "name": "date",
      "type": "date",
      "required": true,
      "example": "13 Aug 2026"
    },
    {
      "name": "status",
      "type": "text",
      "required": true,
      "example": "For decision",
      "notes": "e.g. For decision / Decided / Draft."
    },
    {
      "name": "situation",
      "type": "html",
      "required": true,
      "example": "<p>The sales team tracks leads in a spreadsheet…</p>",
      "notes": "1 short paragraph of neutral facts."
    },
    {
      "name": "complication",
      "type": "html",
      "required": true,
      "example": "<p>The team doubles by Q2 2027…</p>",
      "notes": "1 short paragraph: why act now."
    },
    {
      "name": "decision-required",
      "type": "text",
      "required": true,
      "example": "Select and contract a CRM platform before 1 September 2026.",
      "notes": "One sentence, with deadline/constraint."
    },
    {
      "name": "recommendation",
      "type": "html",
      "required": true,
      "example": "<p><strong>Choose HubSpot Starter.</strong> It fits the budget…</p>",
      "notes": "Start with the recommended option in <strong>, then 2–3 sentences of why."
    },
    {
      "name": "risks-content",
      "type": "html",
      "required": false,
      "example": "<p>Adoption risk — mitigate by…</p>",
      "notes": "Inside the risks optional block."
    },
    {
      "name": "footer-note",
      "type": "text",
      "required": false,
      "example": "Confidential — internal use"
    }
  ],
  "repeats": [
    {
      "name": "option",
      "description": "One row per option considered.",
      "min": 2,
      "max": 4,
      "slots": [
        {
          "name": "option-name",
          "type": "text",
          "required": true,
          "example": "HubSpot"
        },
        {
          "name": "option-summary",
          "type": "text",
          "required": true,
          "example": "Starter CRM suite; marketing tools included."
        },
        {
          "name": "option-pros",
          "type": "html",
          "required": true,
          "example": "<ul><li>Fastest onboarding</li></ul>",
          "notes": "<ul> with max 3 short <li>."
        },
        {
          "name": "option-cons",
          "type": "html",
          "required": true,
          "example": "<ul><li>Costs rise at scale</li></ul>",
          "notes": "<ul> with max 3 short <li>."
        },
        {
          "name": "option-cost",
          "type": "text",
          "required": true,
          "example": "€6.2k/yr at 14 seats; ~1 wk migration"
        }
      ]
    },
    {
      "name": "step",
      "description": "One row per next step.",
      "min": 2,
      "max": 6,
      "slots": [
        {
          "name": "step-action",
          "type": "text",
          "required": true,
          "example": "Start free-tier pilot with 3 reps"
        },
        {
          "name": "step-owner",
          "type": "text",
          "required": true,
          "example": "Sanne"
        },
        {
          "name": "step-due",
          "type": "text",
          "required": true,
          "example": "20 Aug"
        }
      ]
    }
  ],
  "optionals": [
    {
      "name": "risks",
      "description": "Key risks & mitigations panel at the bottom. Remove if the user provides none and none are evident."
    }
  ],
  "tags": [
    "work",
    "management"
  ],
  "changelog": [
    {
      "version": "0.1.0",
      "date": "2026-08-13",
      "notes": "Initial release: situation/complication, options table, highlighted recommendation, next steps and risks."
    }
  ],
  "agentInstructions": "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.",
  "license": "MIT",
  "authors": [
    {
      "github": "bvrln"
    }
  ]
}