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 reasonably well-constructed description with a clear 'Use when' clause and good trigger terms for the product vision domain. Its main weaknesses are that the capability description leans on adjectives rather than concrete actions (what specific outputs does it produce beyond brainstorming?), and it could potentially overlap with broader product strategy or planning skills.
Suggestions
Add more specific concrete actions beyond 'brainstorm' — e.g., 'generates vision statements, creates vision canvases, defines success metrics for the vision'
Differentiate more clearly from adjacent product management skills by specifying what this skill does NOT cover (e.g., roadmapping, strategy frameworks) or by adding more distinctive trigger terms
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (product vision) and some actions ('brainstorm', 'defining or refining', 'creating a vision statement', 'aligning the team'), but the core capability description uses adjectives ('inspiring, achievable, emotional') rather than listing multiple concrete distinct actions. It doesn't specify what concrete outputs or steps are involved beyond brainstorming. | 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 around a shared direction). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms a user would say: 'product vision', 'vision statement', 'aligning the team', 'shared direction', 'stakeholders', 'defining or refining'. These are terms users would naturally use when seeking help with product vision work. | 3 / 3 |
Distinctiveness Conflict Risk | While 'product vision' is fairly specific, it could overlap with skills related to product strategy, product roadmapping, or general brainstorming/ideation skills. The terms 'aligning stakeholders' and 'shared direction' are somewhat generic and could trigger for broader product management or strategy 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 brainstorming product visions but lacks concrete examples (e.g., sample vision statements showing good vs. bad), which significantly limits actionability. The content includes some unnecessary explanation of concepts Claude already understands, and the external links are not accessible to Claude. The workflow is clear but would benefit from explicit validation/iteration steps with the user.
Suggestions
Add 2-3 concrete example vision statements (good and bad) to demonstrate the desired output format and quality level, significantly improving actionability.
Remove the 'Domain Context' section or reduce it to a single sentence — Claude understands what a product vision is.
Add a validation/feedback step in the process, e.g., 'Present draft visions to the user and iterate based on feedback before selecting the final version.'
Replace external URLs with inline guidance or remove them, since Claude cannot access external links during execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., the 'Domain Context' section explaining what a vision is, the metadata block repeating the description). The 'Notes' section is somewhat useful but borders on things Claude already knows about good communication. Could be tightened. | 2 / 3 |
Actionability | The process steps provide a reasonable sequence but remain abstract — there are no concrete examples of vision statements, no templates, no before/after examples. For an instruction-only skill, the guidance should be more specific (e.g., example inputs and example vision statement outputs) to reach a score of 3. | 2 / 3 |
Workflow Clarity | The 6-step process is clearly sequenced and reasonable for a non-destructive brainstorming task. However, there are no validation checkpoints — no step to verify the vision against criteria, no feedback loop for iterating with the user, and no explicit checkpoint for user approval before finalizing. | 2 / 3 |
Progressive Disclosure | The 'Further Reading' section references external URLs (not bundle files), which aren't actionable for Claude. There are no bundle files, and the content is all inline in a single file. For a skill of this length (~50 lines of content), this is acceptable but the external links add little value since Claude can't access them. | 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
d384f0c
- 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.