The leadership-facing decision artifact. RFCs are for engineers; ADRs are for posterity; decision memos are for the person with 5 minutes to decide.
When to use
Bringing a decision to an exec / sponsor / committee for ratification.
Pre-meeting brief: leader will see this before the meeting to come prepared.
The strategic recommendation from stakeholder-update-writer exec tier needs a backing one-pager.
When NOT to use
Technical decision capture → adr-writer.
Open-for-comment proposal → rfc-writer.
Exception request → exception-request-drafter.
Stakeholder update across many topics → stakeholder-update-writer.
Document structure (one page, 250-500 words)
# Decision Memo — {title}
**Decision needed**: {1 sentence — what the leader must decide}
**Decision-maker**: {role + name}
**Recommended decision**: {1 sentence — author's recommendation}
**Date**: YYYY-MM-DD
**Author / sponsor**: {names}
## Context (~60 words)
{What's the backdrop. Cite relevant vault notes.}
## Options
1. **{Option A}** — pros / cons / cost
2. **{Option B}** — pros / cons / cost
3. **{Option C — recommended}** — pros / cons / cost (+ why this one)
## Risk of inaction
{What happens if no decision is made? Cite the specific risk.}
## Asks
- Decision needed by: {date}
- If approved: {what unlocks immediately}
- If rejected: {what alternative path is needed}
## Sources
- {vault notes — research, facts, prior decisions}
As the final step, write the memo via vault-writer.write_insight to vault/insights/YYYY-MM-DD-decision-memo-{slug}.md (it informs a decision; the decision itself becomes a separate decisions/ ADR).
Composes with
vault-querier — pull supporting facts / research.
vault-writer.write_insight — persists the memo (final step).
stakeholder-update-writer — exec-tier outputs sometimes need decision-memo backup.
adr-writer — once the decision is made, the ADR captures it.
Acceptance test (for step 32 done-criteria)
One live decision memo. Natural fixture: the AI-governance position quarterly recommendation that needs a leader to choose between active/passive postures.
1---2name: decision-memo-writer3description: decision-memo-writer4---56# decision-memo-writer78The leadership-facing decision artifact. RFCs are for engineers; ADRs are for posterity; decision memos are for the person with 5 minutes to decide.910## When to use1112- Bringing a decision to an exec / sponsor / committee for ratification.13- Pre-meeting brief: leader will see this before the meeting to come prepared.14- The strategic recommendation from `stakeholder-update-writer` exec tier needs a backing one-pager.1516## When NOT to use1718- Technical decision capture → `adr-writer`.19- Open-for-comment proposal → `rfc-writer`.20- Exception request → `exception-request-drafter`.21- Stakeholder update across many topics → `stakeholder-update-writer`.2223## Document structure (one page, 250-500 words)2425```markdown26# Decision Memo — {title}2728**Decision needed**: {1 sentence — what the leader must decide}29**Decision-maker**: {role + name}30**Recommended decision**: {1 sentence — author's recommendation}31**Date**: YYYY-MM-DD32**Author / sponsor**: {names}3334## Context (~60 words)35{What's the backdrop. Cite relevant vault notes.}3637## Options381. **{Option A}** — pros / cons / cost392. **{Option B}** — pros / cons / cost403. **{Option C — recommended}** — pros / cons / cost (+ why this one)4142## Risk of inaction43{What happens if no decision is made? Cite the specific risk.}4445## Asks46- Decision needed by: {date}47- If approved: {what unlocks immediately}48- If rejected: {what alternative path is needed}4950## Sources51- {vault notes — research, facts, prior decisions}52```5354As the final step, write the memo via `vault-writer.write_insight` to `vault/insights/YYYY-MM-DD-decision-memo-{slug}.md` (it informs a decision; the decision itself becomes a separate `decisions/` ADR).5556## Composes with5758- `vault-querier` — pull supporting facts / research.59- `vault-writer.write_insight` — persists the memo (final step).60- `stakeholder-update-writer` — exec-tier outputs sometimes need decision-memo backup.61- `adr-writer` — once the decision is made, the ADR captures it.6263## Acceptance test (for step 32 done-criteria)6465One live decision memo. Natural fixture: the AI-governance position quarterly recommendation that needs a leader to choose between active/passive postures.
Run npx skillmds@latest add themarmack/decision-memo-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
decision-memo-writer It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
themarmack (@themarmack) published this skill. Their other Agent Skills are listed on their SkillMD profile.