Write the decision memo
Turn a fuzzy debate into one explicit choice, its evidence, trade-offs, and next move.
Use this when
A document that describes context but never names the choice
Assumptions written in the same voice as observed facts
A recommendation with no next test or condition that could change it
The quality gate
- One decision is stated as a choice, with an owner and a decision date
- Observed facts, interpretations, and assumptions are visibly separated
- Two or three credible options are compared, including doing nothing when relevant
- Trade-offs, risks, reversibility, and the cost of delay are explicit
- The recommendation ends with the next evidence-producing action and its stop condition
Prove it: Give the memo to someone outside the discussion; they must identify the choice, recommendation, strongest evidence, and next action without explanation.
Install or copy
Save the download as decision-memo/SKILL.md in your agent's supported skills directory, or copy the complete package below. Load it only when its description matches the work.
--- name: decision-memo description: "Structures a product or business choice into an evidence-backed decision memo with options, trade-offs, a recommendation, and next test. Use when a team is debating direction or needs to record why one option should be chosen." --- # Write the decision memo Apply this skill during **Discovery** work. It supports Any stack. Turn a fuzzy debate into one explicit choice, its evidence, trade-offs, and next move. ## Instructions Write a decision memo before proposing more work. State the single decision, owner, and decision date. Separate observed facts from interpretations and assumptions, citing the source and freshness of each fact. Compare two or three credible options, including doing nothing when it is real, across user value, commercial value, effort, risk, reversibility, and cost of delay. Recommend one option in plain language. End with the smallest next action that can produce missing evidence, its success threshold, and the condition that would change or stop the recommendation. Do not hide uncertainty behind confident prose. ## Detect the problem - A document that describes context but never names the choice - Assumptions written in the same voice as observed facts - A recommendation with no next test or condition that could change it ## Hold the gate Do not declare this phase complete until every item passes: - [ ] One decision is stated as a choice, with an owner and a decision date - [ ] Observed facts, interpretations, and assumptions are visibly separated - [ ] Two or three credible options are compared, including doing nothing when relevant - [ ] Trade-offs, risks, reversibility, and the cost of delay are explicit - [ ] The recommendation ends with the next evidence-producing action and its stop condition ## Verify the result Give the memo to someone outside the discussion; they must identify the choice, recommendation, strongest evidence, and next action without explanation.
More discovery skills
The one-page problem brief
No code until the problem fits on one page a stranger understands.
Steal the bar, not the pixels
Tear down the three best competitors before designing anything.
Map the riskiest assumption
Find the belief most likely to waste the loop, then test it before polishing anything else.
Want this quality gate applied to a real product decision?
Start a First Loop