product-vision
Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders. Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction.
73
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./pm-product-strategy/skills/product-vision/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates both what the skill does and when to use it, with good trigger terms that users would naturally employ. Its main weaknesses are somewhat abstract capability language (relying on adjectives like 'inspiring' and 'emotional' rather than concrete actions) and moderate overlap risk with adjacent product management skills.
Suggestions
Add more concrete actions/deliverables to improve specificity, e.g., 'Generates vision statements, crafts elevator pitches, produces vision documents with success metrics and timeframes'
Differentiate more clearly from adjacent product strategy skills by specifying what this skill does NOT cover (e.g., roadmapping, OKRs, competitive analysis)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (product vision) and some actions ('brainstorm', 'defining or refining', 'creating a vision statement', 'aligning the team'), but the actions are somewhat abstract—'inspiring, achievable, and emotional' are more adjectives than concrete capabilities. It doesn't list specific deliverables or techniques. | 2 / 3 |
Completeness | Clearly answers both 'what' (brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders) and 'when' (explicit 'Use when' clause covering defining/refining a product vision, creating a vision statement, or aligning the team). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'product vision', 'vision statement', 'aligning stakeholders', 'shared direction', 'defining or refining a product vision'. These cover the most common ways a user would phrase this need. | 3 / 3 |
Distinctiveness Conflict Risk | While 'product vision' and 'vision statement' are fairly specific, there could be overlap with skills related to product strategy, product roadmapping, or general brainstorming/ideation skills. The terms 'aligning stakeholders' and 'shared direction' are broad enough to potentially conflict with other product management skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for product vision brainstorming but lacks concrete examples (e.g., sample vision statements showing good vs. bad), specific evaluation criteria, and iteration/feedback loops. The content explains concepts Claude already understands and could be significantly tightened while adding more actionable, example-driven guidance.
Suggestions
Add 2-3 concrete example vision statements (good and bad) so Claude has clear quality benchmarks to aim for when generating output.
Include a validation/iteration step where Claude presents draft visions and asks the user for feedback before selecting the strongest option.
Remove the 'Domain Context' section and generic 'Notes' — Claude already knows what a product vision is; replace with specific patterns or templates that differentiate great visions from mediocre ones.
Add an example input/output pair showing what $ARGUMENTS might look like and what the final deliverable should contain.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Domain Context' section explaining what a vision is, which Claude already knows). The 'Notes' section contains generic advice that a veteran product leader would already know. However, it's not excessively verbose. | 2 / 3 |
Actionability | The process steps provide a reasonable sequence but remain fairly abstract — there are no concrete examples of vision statements, no templates, no before/after examples. For an instruction-only skill, the guidance could be much more specific (e.g., showing example inputs and example vision statement outputs). | 2 / 3 |
Workflow Clarity | The 6-step process is listed clearly, but there are no validation checkpoints or feedback loops. For a brainstorming/creative task, there's no step for user review or iteration, and no criteria for evaluating whether a draft vision meets the inspiring/achievable/emotional criteria. | 2 / 3 |
Progressive Disclosure | The 'Further Reading' section links to external resources, but these are external URLs (not project files) and aren't clearly signaled as optional deep-dives. The content is reasonably organized with sections, but the inline content could benefit from better separation between quick-start guidance and detailed process. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- phuryn/pm-skills
- Commit
36ccefd
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.