Define product vision
Skill alexe-ev/product-plugins/product-strategy/skills/define-product-vision
Turn organizational goals and user insights into a clear product vision and mission statement. Use this skill when a team needs to articulate where the product is going and why it exists.From its SKILL.md
npx -y skills add alexe-ev/product-plugins --skill define-product-visionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.8 KB, 553 tokens by cl100k_base, as published. Nobody here has run it
Define Product Vision
Purpose
Help teams articulate a clear, actionable product vision and mission that aligns stakeholders and guides long-term decisions.
Skill type
Conceptual skill
Use this skill when
- A product or team lacks a clear vision statement
- The existing vision is vague, outdated, or misaligned with strategy
- The team is starting a new product or major pivot
- Leadership needs a unifying narrative for the product direction
Do not use this skill when
- The team already has a strong, agreed-upon vision
- The user needs roadmap-level prioritization (use build-portfolio-roadmap-strategy)
- The user needs competitive positioning (use frame-competitive-differentiation)
Required inputs
- Product area or domain
- Target user or customer segment
- Business goal or organizational context
Optional inputs
- Existing mission/vision drafts
- Key user problems or insights
- Company-level strategy
- Competitive landscape notes
- Time horizon for the vision
Upstream context
Works best when at least some of the following exist:
- Known target user segment
- Known product area
- Business or organizational goal
If upstream context is missing
If no product area, segment, or goal is provided, do not invent a confident vision. Produce a provisional draft and explicitly list what must be confirmed before the vision can be finalized.
Downstream handoff
Output from this skill can feed:
- assess-product-market-fit
- build-portfolio-roadmap-strategy
- frame-competitive-differentiation
A good handoff includes:
- Vision statement
- Mission statement (optional)
- Target user and problem
- Strategic time horizon
- Open questions
Instructions
- Identify the target user and core problem being solved.
- Identify the desired long-term outcome for users and the business.
- Identify the strategic time horizon (1-year, 3-year, 5-year+).
- Draft a vision statement: aspirational, user-centric, not tied to specific features.
- Draft a mission statement: what the product does and for whom today.
- Check for clarity, specificity, and differentiation.
- List what is still missing or needs validation.
Output
Provide:
- Vision statement
- Mission statement
- Target segment
- Core user problem addressed
- Strategic time horizon
- Confidence level: provisional / context-informed / ready-to-align
- Missing context or open questions
Risks / caveats
- Do not write a vision that describes features, not outcomes
- Do not present the vision as final if key strategic context is missing
- Avoid generic statements that could apply to any product
What ships with it: 3 files
3.5 KB alongside SKILL.md