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.
58
66%
Does it follow best practices?
Impact
—
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 slightly abstract capability language (relying on adjectives like 'inspiring' and 'emotional' rather than concrete actions) and moderate overlap risk with other product strategy skills.
Suggestions
Add more concrete actions or deliverables, e.g., 'generates vision statements, creates vision canvases, defines success metrics' to improve specificity.
Differentiate from adjacent product strategy skills by explicitly noting what this skill does NOT cover, or by adding more distinctive trigger terms like 'north star', 'product purpose', or 'long-term product direction'.
| 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 keywords users would say: 'product vision', 'vision statement', 'aligning stakeholders', 'shared direction', 'defining or refining a product vision'. These are terms a user would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | While 'product vision' and 'vision statement' are fairly specific, this could overlap with broader product strategy, roadmapping, or general brainstorming skills. The niche is reasonably clear but not entirely distinct from adjacent 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 stays at a fairly abstract level. It lacks concrete examples of good vision statements (input/output pairs) that would make it truly actionable, and includes some unnecessary explanatory content that Claude already knows. The workflow is clear but would benefit from iteration/feedback steps and example outputs.
Suggestions
Add 2-3 concrete example vision statements with input context and output, showing what a good result looks like (e.g., 'For a fintech startup targeting underbanked populations: "A world where everyone has access to financial tools that build generational wealth"').
Remove the 'Domain Context' section or reduce it to one line — Claude already understands what a product vision is.
Replace the external 'Further Reading' links with actionable templates or frameworks that Claude can directly use during execution (e.g., a vision statement template or evaluation criteria checklist).
Add an explicit feedback/iteration step in the process, such as 'Present options to the user, gather feedback, and refine the strongest candidate.'
| 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, iteration, or refinement based on feedback. The sequence is present but lacks explicit checkpoints. | 2 / 3 |
Progressive Disclosure | The 'Further Reading' section references external links (not project files), which aren't useful for Claude during execution. The content is all inline in a single file, which is acceptable for this skill's length, but the external links add no actionable value and the structure could be tighter. | 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
020ee82
- 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.