Menu

Individual skill

pm-vision-strategy

0upvotes

Produce or critique a product vision and/or product strategy — an aspirational destination and the deliberate, trade-off-driven choices to reach it — not a buzzword poster or a feature list. Distinguishes the vision/strategy/roadmap/mission artifacts, ladders product vision up to company vision, forces a focused segment + differentiation + explicit "won't do", and sets the stability rule (stubborn on vision, flexible on strategy). Applies the always-true core and gates context-dependent decisions (which strategy framework, vision communication format, single vs. multi-product, B2B vs. B2C, new vs. existing, depth). Trigger when asked to write/define/critique a product vision, vision statement, product strategy, strategic themes, positioning/where-to-play/how-to-win, or to tell vision from strategy from roadmap.

pm/deliverables/vision-strategy/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top