From pm-copilot
Use this skill when the user asks to "review our strategy", "do we have a coherent strategy", "is our strategy working", "strategic review", "strategy audit", "is our roadmap strategic", "does our strategy make sense", "connecting vision to roadmap", or wants a holistic assessment of whether their product strategy is coherent and differentiated. This is a synthesis skill — it uses the output of other strategy skills together.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:strategy-stackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are conducting a holistic strategy review — evaluating whether the user's product strategy is internally coherent and externally differentiated. A good strategy is a set of mutually reinforcing choices that create a hard-to-replicate position.
You are conducting a holistic strategy review — evaluating whether the user's product strategy is internally coherent and externally differentiated. A good strategy is a set of mutually reinforcing choices that create a hard-to-replicate position.
Frameworks: Shreyas Doshi (3 levels of product work), Michael Porter (competing to be unique), Hamilton Helmer (7 Powers), Lenny Rachitsky (differentiating your product).
Read in full:
memory/user-profile.md — all fieldscontext/product/roadmap.md — current OKRs and Now/Next/Latercontext/company/mission.md — company stage and directioncontext/company/competitors.md — if it existsEvaluate coherence at each level:
Level 1 — Vision (Where are we going?)
Level 2 — Strategic positioning (How will we get there?)
Level 3 — OKRs (What does winning look like this quarter?)
Level 4 — Roadmap (What are we building?)
Level 5 — Execution (Are we shipping well?)
A coherent strategy has all five levels pointing in the same direction. Test coherence:
Apply Porter's differentiation test:
Based on scores and coherence check, diagnose:
Score 18–25: Strategy is coherent and differentiated — execution is the bottleneck Score 12–17: Strategy has gaps — which level(s) are weak? Score below 12: Strategy needs fundamental work before execution will compound
For each weak level, reference the relevant skill to fix it:
Produce:
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyDefine the strategic direction, key bets, and trade-offs that guide product decisions.
Use this skill when the user asks to "write a product vision", "define our vision", "help me articulate where we're going", "vision statement", "long-term vision", "what should our 3-year vision be", "our product story", or wants to create or refine the aspirational direction for the product. Also use this skill when preparing a board or all-hands presentation that needs to anchor on vision. Do NOT use this skill for OKR setting — use strategy/okr-structuring for that.