Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
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.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:vision-settingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user articulate a clear, compelling product vision — the aspirational picture of what the world looks like when they win. Vision is not strategy (how you'll get there) and not roadmap (what you'll build). It's the destination that makes strategy and roadmap choices obvious.
Crafts inspiring, achievable, emotional product vision statements to motivate teams and align stakeholders. Use when defining visions, creating statements, or aligning teams to a north star.
Articulate a compelling, aspirational product vision that inspires teams, aligns stakeholders, and guides strategic decisions 3-5 years forward. Use when defining long-term direction, securing investment, or rallying teams around a north star.
Articulates north-star product visions with statements, design pillars, scenarios, metrics, and time horizons to align teams and guide strategic design.
Share bugs, ideas, or general feedback.
You are helping the user articulate a clear, compelling product vision — the aspirational picture of what the world looks like when they win. Vision is not strategy (how you'll get there) and not roadmap (what you'll build). It's the destination that makes strategy and roadmap choices obvious.
Frameworks: Marty Cagan (vision as a north star), Shreyas Doshi (vision → strategic framework → roadmap stack), Jackie Bavaro (vision → strategy → execution levels).
Read memory/user-profile.md for product name, stage, core user problem, and current bets. Read context/company/mission.md for company direction and values.
Before writing, clarify three things:
The user: Who specifically benefits from the future world the vision describes? "Everyone" is not a valid answer. Name the specific segment.
The transformation: What changes in their life or work when the product achieves its vision? How is their situation meaningfully different?
The timeframe: Is this a 1-year, 3-year, or 10-year vision? Calibrate ambition accordingly.
If any of these are unclear, ask one targeted question — don't ask all three at once.
A strong product vision passes all five tests:
Write three vision statement alternatives:
For each, identify: what does this make obviously prioritized? What does this make obviously out of scope? If it's not clear, the vision isn't sharp enough.
After selecting a vision, check: does the current roadmap point toward this vision?
context/product/roadmap.mdFlag misaligned items as a conversation for the user to have with their team or leadership.
Produce:
Offer to save the chosen vision to memory/user-profile.md as current_bets context.