Write a decision memo
Writes a one-page decision memo with the decision needed and by when, context, options with honest trade-offs, a recommendation and next steps. Use when asking a manager to approve something.
A decision memo exists to get a clear yes, no or choice from a busy person in a few minutes. It fails when the decision is buried under background, when the options are a straw man next to the favourite, when costs and risks are vague, or when the reader has to write back to ask what exactly they are approving. Good memos put the ask and the deadline in the first lines, compare real options on the same criteria, admit the downside of the recommendation, and say what happens next under each answer.
Write a one-page decision memo.
Only if [OPTIONS] is given:
Only if [DECISION_MAKER] is given: Decision-maker:
- If you cannot tell what decision is needed or the situation gives no facts to weigh (only feelings or a general complaint), ask up to three short questions and stop. Missing options are not a reason to stop: propose them in step 4. A missing decision-maker is not either: address the memo to
[NEEDED: decision-maker], write for a busy senior reader who knows the business but not this issue, and say so under Gaps. - State the decision as one question with a yes, no or choice answer, and the date it is needed by (with the reason for that date, such as a notice period or a release date in the situation). If no date can be derived, mark
[NEEDED: decide-by date]. - Write the context the decision-maker needs and nothing more: three to six sentences on what is happening, why it matters now, and the cost of not deciding. Fit it to what the decision-maker already knows and cares about.
- Lay out two to four genuine options. Always include "do nothing" or "delay" if it is realistic. Compare them on the same criteria (cost, benefit, risk, time, reversibility, effect on people or customers), using only figures from the situation and marking unknowns.
- Recommend one option and give the deciding reason in one or two sentences. Name its main downside and how it will be managed. If the facts do not support a clear recommendation, say what would settle it.
- Write next steps if approved: who does what by when, and the first checkpoint where the decision could be revisited.
- One page: about 350 to 500 words for the memo itself.
- Use only the facts supplied. Never invent costs, dates, percentages or names; mark each gap
[NEEDED: …]and list it. - Present options fairly. Do not weaken the alternatives to make the recommendation look better; if an option is clearly not viable, say why in one line.
- Plain, neutral language. No hype, no hedging, no "synergies". Numbers in figures, with units.
- If the decision touches legal, HR, safety or regulatory obligations, note who must also sign off.
Memo
To / From / Date / Decision needed by (names and dates from the situation, otherwise [NEEDED: …])
Decision needed: one question.
Recommendation: one sentence.
Context: short paragraph.
Options: a table with options as rows and the criteria as columns, then one line per option on its main risk.
Why this recommendation: two to four sentences, including its downside.
Next steps if approved: numbered, each with owner and date.
Gaps to fill
Each [NEEDED: …] with what it is and where to get it. "None" if none.
Before you send
Two or three checks specific to this memo (for example "confirm the vendor price is still valid").
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Business writing
- level
- Intermediate
- made for
- People manager, Product manager, Operations, Executive / leader
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install write-decision-memo --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-decision-memo -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Business writingWrite an executive summary
Writes an executive summary of a long document that leads with the bottom line, the key points and the ask, using only facts from the source. Use before sending a report to busy readers.
write-executive-summaryWrite a project proposal or business case
Writes an internal project proposal or business case covering the problem, options, recommendation, cost, benefits and risks, and marks every missing number instead of inventing it.
write-project-proposalWrite an escalation email
Writes an escalation to a manager, vendor or another team that states the issue, its impact, what was already tried and the specific decision or help needed by a date, without blame.
write-escalation-emailEditor
Editor who serves the reader and the author's intent, edits at the right level with structure before lines, and explains every change so the author can accept, reject or learn from it.
editorWrite an internal announcement
Writes an internal announcement of a reorg, policy change or launch that explains what is changing, why, the impact on each group and where to ask, plus an FAQ and a pre-send check.
write-internal-announcementWrite a project status report
Writes a project status report with an evidence-based RAG status, progress, risks, decisions needed and next steps, formatted as an email, a document or a single slide.
write-status-report