Product Vision & Strategy Skill

How this skill behaves (read first)

This is a generative skill, and vision/strategy is where an AI assistant produces its most confident, least useful output. Two default failure modes dominate:

1. The inspirational poster. Asked for a vision, Claude writes a buzzword sentence — "be the world's most loved, best-in-class platform that delights customers with seamless experiences" — that sounds good and guides zero decisions. If any feature can be justified by it, it's too vague to be a vision.
2. Conflation and feature-listing. Claude treats vision, strategy, roadmap, and mission as interchangeable, and writes "strategy" as a list of features to build rather than a set of deliberate choices about where to play, how to win, and what not to do. Strategy that targets "everyone" and skips trade-offs isn't strategy.

A real vision is a specific, stable, user-centric destination; a real strategy is a focused set of interconnected, trade-off-driven choices grounded in evidence and tied to outcomes. So this skill gates:

1. Establish context — vision, strategy, or both; company shape; product stage; market type; altitude.
2. Apply the always-true core — the artifact distinctions, the laddering, the focus-and-trade-off discipline, the stability rule.
3. Surface the context-dependent decisions (which framework, which communication format, portfolio/B2B/stage/depth) with trade-offs, and let the user choose. Running every framework at once is the failure mode.

Then it hands off to pm-okr-metric-validity-audit (the success metrics it names), pm-prioritization-rigor-audit (the themes/focus areas it sets, which drive what gets built), and pm-assumption-rigor-audit (the market-demand and competitive bets the strategy rests on).

Scope: this skill owns the vision artifact and the strategy artifact, and the choices inside them. It defers the competitive/market analysis that feeds strategy to pm-competitive-analysis, the research/insight-gathering to pm-discovery, problem framing to pm-problem-statement, the prioritization decision itself to pm-prioritization, the OKR/KPI artifacts to pm-okrs-kpis, the roadmap artifact and sequencing to pm-roadmap, pricing to ux-pricing, and go-to-market to pm-gtm-plan.