product-vision
by phurynUse the product-vision skill to brainstorm an inspiring, achievable, and emotional product vision for Product Management. It helps teams create a vision statement, align around a north star, and refine strategy with real company and product context.
This skill scores 68/100, which means it is acceptable to list but best framed as a limited, single-purpose workflow. Directory users can expect clear intent and a usable prompt for product-vision drafting, though they should not expect much supporting infrastructure or procedural depth beyond the core instruction set.
- Clear triggerability: the metadata and triggers explicitly target product vision, vision statement, and north-star alignment use cases.
- Operationally usable: the skill provides a defined role, input requirements, and a three-part output standard (inspiring, achievable, emotional).
- Good install decision value: the body is substantial, with multiple headings and no placeholder markers, suggesting real workflow content rather than a stub.
- Light supporting evidence: there are no scripts, references, resources, or examples, so users must trust the written guidance without external validation.
- Limited execution detail: the excerpt shows process steps, but little constraint handling or edge-case guidance, which may still leave some guesswork for agents.
Overview of product-vision skill
What product-vision does
The product-vision skill helps you brainstorm a product vision that is inspiring, achievable, and emotional. It is useful when you need a north star, a vision statement, or a clearer shared direction for Product Management work rather than a feature list or roadmap.
Who should use it
Use the product-vision skill if you are a product manager, founder, PM lead, or cross-functional team member trying to align people around what the product is becoming. It is strongest when you have some company or product context and need a better strategic narrative, not a blank-page slogan.
When it is a good fit
This skill fits early strategy work, vision refreshes, and team alignment sessions where the output must motivate people and still be credible. It is less useful if you only need a short marketing tagline, a generic mission statement, or a detailed execution plan.
How to Use product-vision skill
Install and open the right file
Use the product-vision install path from the directory, then start with SKILL.md. For this repo, there are no supporting scripts or resources, so the main value is in reading the skill instructions closely and feeding them strong context.
Give the skill real product context
The skill asks for information about your company and product, plus current state or market positioning. A weak prompt says, “Write a product vision for my app.” A stronger prompt says, “We are a B2B SaaS tool for operations teams; we help reduce manual reporting; the company wants to expand from task automation into decision intelligence; competitors emphasize speed, but we want trust and clarity.”
Shape your prompt for better output
For product-vision usage, include the audience, product stage, market tension, and what emotion the vision should evoke. For example: “Create a product vision for a seed-stage healthcare scheduling platform used by clinic admins. The vision should feel calm, credible, and ambitious, and should support alignment with engineering and sales.”
Workflow that gives the best result
Read SKILL.md first, then supply one concise brief with company context, product scope, user problem, and constraints. If the first result is too broad, iterate by narrowing the customer segment, naming the strategic tradeoff, or asking for a vision that matches a specific tone such as bold, pragmatic, or human-centered.
product-vision skill FAQ
Is product-vision for Product Management only?
No. The product-vision for Product Management use case is the main one, but founders, design leaders, and strategy teams can use it when they need a shared direction that is emotionally compelling and still realistic.
How is this different from a generic prompt?
A generic prompt can produce a vision statement, but the product-vision skill gives you a clearer structure: it expects context, centers aspiration without losing feasibility, and pushes toward a statement that can actually align a team.
What should I avoid when using it?
Do not feed it only slogans, audience adjectives, or competitor names. Without product context and current state, the output will usually sound polished but ungrounded.
Is it beginner-friendly?
Yes, if you can describe your product in plain language. Beginners usually get better product-vision guide results by sharing a simple problem statement, who the user is, and what change the product should make in their world.
How to Improve product-vision skill
Provide sharper strategic inputs
The best improvements usually come from better inputs, not more iterations. State the target user, the business goal, the current constraint, and the emotional tone you want. For example: “We need a vision for an AI assistant for legal ops that feels trustworthy, not flashy, because adoption depends on compliance teams.”
Tell it what success should sound like
If you want a vision you can use in leadership reviews, investor conversations, or team planning, say so up front. A vision meant for internal alignment should sound different from one meant to energize a launch narrative, and product-vision responds better when that audience is explicit.
Fix common failure modes
If the result is vague, add a sharper market reality or user pain. If it is too ambitious, add constraints such as team size, timeline, or technical limits. If it is too abstract, ask for a vision tied to a real user outcome and a believable future state.
Iterate from a working draft
Use the first output as a draft, then refine one dimension at a time: clarity, emotional pull, realism, or audience fit. For product-vision skill work, small targeted revisions usually produce a much better final vision than restarting from scratch.