skills/strategy-memo/SKILL.md
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.
npx skillsauth add mohitagw15856/pm-claude-skills strategy-memoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Ask for these only if they aren't already provided:
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.
Good Strategy / Bad Strategy (Richard Rumelt) — diagnosis, guiding policy, coherent action; and the discipline of explicit non-goals.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.