pm-vision-strategy

Generate and critique product vision and strategy artifacts with trade-off-driven choices.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-vision-strategy-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-vision-strategy
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/deliverables/vision-strategy
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-vision-strategy-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants tend to produce vague, buzzword-filled vision statements and feature lists disguised as strategy. This Skill enforces the discipline of a trained product manager: a specific, user-centric vision that can reject features, and a strategy built on focused segments, defensible differentiation, and explicit trade-offs about what not to do. ## Core Features & Use Cases - Artifact Distinction: Keeps vision, strategy, roadmap, and mission separate and ladders product vision up to company vision. - Context-Gated Decisions: Surfaces framework choices (Playing to Win, Porter's Five Forces, Blue Ocean, Kano, Three Horizons), communication formats, and B2B/B2C or single/multi-product adaptations with trade-offs instead of applying everything at once. - Audit Hand-offs: Routes the result to assumption-rigor, OKR metric validity, and prioritization rigor audits before declaring it done. - Use Case: Ask for a product strategy for a pre-PMF B2B SaaS tool and receive one primary segment, a differentiation bet with a "can't or won't" defense, 3-5 focus areas, and an explicit list of what you will not build. ## Quick Start Ask the assistant to write a product vision and strategy for your product, stating whether it is B2B or B2C, new or existing, and single or multi-product.

Frequently Asked Questions about pm-vision-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product vision statement that is not vague?▼

Write a specific, user-centric destination describing the changed user future in plain language anyone can repeat. Apply the decision-filter test: if any feature could be justified by the statement, tighten it until a feature clearly aligns or conflicts.

What is the difference between product vision, strategy, and roadmap?▼

Vision is the aspirational destination stable for 3-5 years, strategy is the set of choices about where to play and how to win reviewed quarterly, and the roadmap is what gets built and when. They form a hierarchy from company vision down to features.

Which product strategy framework should I use?▼

Pick one or two frameworks that answer your actual question: Playing to Win for a full strategy, Porter's Five Forces for industry defense, Blue Ocean for uncontested space, or Kano for feature classification. Running every framework at once is framework theater that buries the real choices.

How does product strategy differ for B2B vs B2C products?▼

B2B strategy serves multiple stakeholders including end users, champions, and economic buyers, with longer cycles and higher switching costs. B2C weights individual decision-makers, viral acquisition, and network effects, so the strategic emphasis must match the buyer reality.

When should a product vision change versus the strategy?▼

Stay stubborn on vision for 3-5 years and flexible on strategy, reviewing it at least quarterly. A vision pivot is rare and happens when the problem itself does not matter to customers, while a discovery pivot changes the path to the same destination and is normal.