mcpField
D
decision-memo-writer

decision-memo-writer

github.com/sylphxaiProductivity162 installsUpdated today
Repository

About decision-memo-writer

A skill for turning product debates with a consequential choice into decision-ready memos. It structures evidence, assumptions, options, risks, and tradeoffs, then records a recommendation and criteria for review or rollback.

Key features

  1. 01Identify the decision owner, scope, and deadline
  2. 02Separate evidence, assumptions, and unknowns
  3. 03Compare options and second-order effects
  4. 04Set success metrics and review triggers

Use cases

  1. 01Resolve a product debate with a clear decision
  2. 02Document options and stakeholder tradeoffs
  3. 03Record review or rollback criteria for a decision

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill decision-memo-writer

After installing, type/decision-memo-writerin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/decision-memo-systems.md

Details

From the project README

Decision Memo Writer

Use this skill to turn ambiguous product debate into a decision-ready memo.

Workflow

  1. Identify decision owner, decision deadline, scope, stakeholders, and whether the decision is reversible.
  2. Read references/decision-memo-systems.md.
  3. Separate facts, assumptions, options, constraints, unknowns, risks, and values.
  4. Compare options with evidence and second-order effects.
  5. Recommend one path, define success metrics, and specify review/rollback triggers.

When not to use

  • Do not use for a status update, meeting summary, brainstorm, or implementation plan when no material choice and accountable decision owner exist.
  • Do not manufacture options merely to fill a template; if the decision is already made, record the decision and evidence boundary directly.

Guardrails

  • Do not present a brainstorm as a decision memo.
  • Do not hide weak evidence, unresolved assumptions, or stakeholder tradeoffs.
  • Do not force consensus when the memo needs a named accountable decision.

Output format

Decision:
Owner/deadline:
Recommendation:

Context:
Options considered:
- <option> -> benefits, costs, risks, evidence

Decision rationale:
Assumptions to validate:
Risks and mitigations:
Success metrics:
Follow-up / revisit trigger:

Comments

Markdown supported