SKILL.md
Policy Memo Skill
A policy memo exists to drive a decision, not to demonstrate research. The decision-maker reads the top and wants: what's the issue, what are my realistic options, what do you recommend, and what happens if I say yes. This skill writes that — BLUF (bottom line up front), honest options with trade-offs, and a defensible recommendation.
Required Inputs
Ask for these only if they aren't already provided:
- The issue / decision — what must be decided and why now.
- The decision-maker — who reads it (minister, exec, board) and what they care about / can authorize.
- Context — relevant background, constraints (legal, budget, political), stakeholders.
- The options — the realistic choices (or ask the skill to develop them), and any evidence/data.
Output Format
MEMO — [subject]
To / From / Date / Re — standard header.
Bottom line (BLUF) — 2–3 sentences: the issue, your recommended option, and the key reason. A busy reader should get the decision from this alone.
Issue — the precise question to be decided, and why it needs a decision now.
Background — only what's needed to decide (concise; detail goes to an annex). Facts, constraints, what's at stake.
Options — 2–4 realistic options (including status quo). For each: what it is, pros, cons, cost/feasibility, and who's affected. A comparison table helps:
| Option | Pros | Cons | Cost / feasibility |
|---|
Recommendation — the option you recommend and why it best fits the goals and constraints. Be decisive; acknowledge the main trade-off you're accepting.
Implementation & risks — key steps, timeline, who does what, and the main risks + mitigations.
Next step / decision requested — exactly what you're asking the reader to approve.