Skip to main content
ClaudeWave
ES, Spanish
Skill1.5k estrellas del repoactualizado 5d ago

strategy-memo

Write a strategy memo that commits to a bet and says what you won't do. Use when asked to write a strategy memo, articulate a strategy, make the case for a strategic direction, or align the team on where to focus. Produces a strategy memo — the strategic question, the diagnosis, the bet/approach, why now, explicit non-goals (what we're NOT doing), how we'll know it's working, and the risks.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/strategy-memo && cp -r /tmp/strategy-memo/plugins/pm-business/skills/strategy-memo ~/.claude/skills/strategy-memo
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Strategy Memo Skill

Strategy is choosing what *not* to do. A real strategy memo makes a bet and names the sacrifices; a fake
one is a list of goals everyone already agreed with. This skill follows the diagnosis → guiding policy →
coherent actions structure, forces explicit non-goals, and ties the bet to leading indicators — so the
team is aligned on a direction sharp enough to be wrong.

## Required Inputs

Ask for these only if they aren't already provided:

- **The strategic question** — the choice or challenge this memo resolves.
- **The situation** — the honest diagnosis: the market, the competition, your real position and constraints.
- **The bet** — the approach you're choosing and what it's betting on being true.
- **The trade-offs** — what you'll deliberately not do or de-prioritise to make the bet.

## Output Format

### Strategy Memo: [the strategic question]

**1. The question** — the strategic choice being made, in one sentence.

**2. Diagnosis** — the honest read of the situation: what's really going on, the few factors that matter most, and your true position (not the aspirational one). A strategy built on a flattering diagnosis fails.

**3. The bet (guiding policy)** — the chosen approach and, explicitly, **what it assumes is true**. This is the spine — everything else serves it.

**4. Why now** — why this is the right bet at this moment (the window, the catalyst), not last year or next.

**5. What we're NOT doing** — the explicit non-goals and de-prioritisations. If this list is empty, it isn't a strategy — it's a wish list.

**6. Coherent actions** — the few moves that follow from the bet and reinforce each other (not a laundry list of everything).

**7. How we'll know** — the leading indicators that tell you the bet is working (or not) early, and the conditions under which you'd reconsider.

**8. Risks** — what could make the bet wrong, and which assumptions to validate first.

## Quality Checks

- [ ] The diagnosis is honest about the real position, not aspirational
- [ ] The bet states what it assumes to be true — it's falsifiable
- [ ] There's an explicit "what we're NOT doing" list with real sacrifices
- [ ] The actions are few and coherent (mutually reinforcing), not an everything-list
- [ ] Leading indicators are named so you learn early whether it's working
- [ ] "Why now" is answered — the timing is justified

## Anti-Patterns

- [ ] Do not write goals and call it strategy — "grow revenue, delight customers" is a wish list, not a bet
- [ ] Do not skip the non-goals — a strategy that sacrifices nothing commits to nothing
- [ ] Do not build on a flattering diagnosis — naming the uncomfortable truth is the hardest and most important part
- [ ] Do not list every initiative — coherent actions reinforce one bet; a long list dilutes it
- [ ] Do not leave the bet unfalsifiable — if no evidence could prove it wrong, it can't be pressure-tested

## Based On

Good Strategy / Bad Strategy (Richard Rumelt) — diagnosis, guiding policy, coherent action; and the discipline of explicit non-goals.
360-feedback-templateSkill

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.

401k-plan-decoderSkill

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.

ab-test-plannerSkill

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.

ab-test-readoutSkill

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.

accessibility-auditSkill

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.

accessible-travel-plannerSkill

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.

accommodation-requestSkill

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.

account-planSkill

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.