decision-memo
Write a crisp decision memo that drives a clear decision, not a discussion. Use when asked to write a decision memo, a recommendation memo, a one/six-pager for a decision, or to get leadership to decide something. Produces a decision memo — the decision & recommendation up front, the context, options with trade-offs, what you'd need to believe, risks, and the explicit ask with a deadline.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/decision-memo && cp -r /tmp/decision-memo/plugins/pm-business/skills/decision-memo ~/.claude/skills/decision-memoSKILL.md
# Decision Memo Skill A decision memo exists to get a decision made — fast, on the record, by the right person. The failure mode is a memo that reads like a discussion: lots of context, no recommendation, no ask. This skill front-loads the recommendation and the decision being requested, then *supports* it — so the reader can say yes, no, or "here's my concern" in five minutes. ## Required Inputs Ask for these only if they aren't already provided: - **The decision** — the specific choice to be made (phrase it as a question with a yes/no or A/B/C answer). - **The recommendation** — your actual recommendation (a memo without one is a status update). - **The options** considered and their trade-offs. - **The decider & deadline** — who owns this call and by when. ## Output Format ### Decision Memo: [the decision] **To:** [decider] · **From:** [you] · **Date:** [date] · **Decision needed by:** [date] **1. Recommendation (TL;DR)** — the recommendation in 2–3 sentences, *first*. What you want them to approve, and the one-line why. **2. The decision** — the question being decided, framed so the answer is a clear choice. **3. Context** — the minimum background needed to evaluate it (link the rest). Why this is on the table now. **4. Options & trade-offs** — a table; be fair to the options you're not recommending (a stacked deck reads as one): | Option | Pros | Cons | Cost / effort | |---|---|---|---| **5. Why this recommendation** — the reasoning, and **what you'd have to believe** for it to be wrong (the assumptions it rests on). **6. Risks & mitigations** — the real downsides and how you'd handle them. A reversible decision deserves less agonising than an irreversible one — say which it is. **7. The ask** — exactly what you need from the reader: approve / pick an option / give input — by the deadline. ## Quality Checks - [ ] The recommendation is in the first paragraph, not the conclusion - [ ] The decision is framed as a clear question with a finite set of answers - [ ] Options not recommended are presented fairly, with real pros - [ ] The memo states what would have to be true for the recommendation to be wrong - [ ] It says whether the decision is reversible (one-way vs. two-way door) - [ ] There is an explicit ask and a decision deadline ## Anti-Patterns - [ ] Do not bury the recommendation at the end — the reader should know what you want in the first 30 seconds - [ ] Do not write a status update disguised as a decision memo — if there's no decision and no ask, it's not this document - [ ] Do not stack the options — strawman alternatives destroy your credibility and the decision's quality - [ ] Do not over-agonise a reversible decision — match the rigor to the cost of being wrong - [ ] Do not hide the assumptions — surfacing "what we'd need to believe" is what lets a decider pressure-test it ## Based On Narrative decision-memo practice (Amazon-style one/six-pagers; one-way vs. two-way door decisions).
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.