borghei/Claude-Skills / project-management/execution/product-vision
product-vision
VerifiedWrite the 5-10 year product vision as a vision board, narrative or elevator pitch, and stress-test it. Use when setting or refreshing long-range direction, or when strategy decks lack a shared picture of where the product is going.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.5 KB |
| assets/elevator_pitch_template.md | markdown | 4.7 KB |
| assets/narrative_vision_template.md | markdown | 4.3 KB |
| assets/vision_board_template.md | markdown | 3.3 KB |
| assets/vision_review_checklist.md | markdown | 4.8 KB |
| examples/helix-platform-vision.md | markdown | 9.4 KB |
| references/red-flags.md | markdown | 10.6 KB |
| references/vision-frameworks-guide.md | markdown | 13.4 KB |
| references/vision-playbook.md | markdown | 15.1 KB |
assets/elevator_pitch_template.md
View on GitHub# Elevator Pitch Template (Geoffrey Moore Positioning Statement)
The single-sentence positioning. If you cannot fill in every blank with a specific answer, the vision is not yet sharp.
---
**Product:** [...]
**Date:** [YYYY-MM-DD]
**Author:** [...]
**Version:** v[X.Y]
---
## The Six-Blank Template
```
For [target customer]
who [statement of need or opportunity],
[product name] is a [product category]
that [statement of key benefit -- compelling reason to buy].
Unlike [primary competitive alternative],
our product [statement of primary differentiation].
```
---
## Fill in the blanks (with discipline)
### 1. Target customer
**Bad (generic):** "businesses", "teams", "everyone in finance"
**Good (specific):** "finance leads at 100-500 person B2B SaaS companies who close monthly"
The target should be specific enough that you can list 20-30 customers (or prospects) who match the description.
| Element | Your answer | Specificity test |
|---------|-------------|-------------------|
| Role | [...] | [Can you name the exact title?] |
| Company context | [...] | [Industry + size + stage?] |
| Frequency context | [...] | [How often do they hit the trigger?] |
**Your target customer:** [final phrasing]
---
### 2. Statement of need / opportunity
**Bad (generic):** "wants to be more efficient", "needs better tools"
**Good (specific):** "loses 11 hours per close to manual reconciliation across 3+ payment processors"
The need should be measurable. If you cannot put a number on it (hours, dollars, frequency, severity), it is too abstract.
**Your statement of need:** [final phrasing]
**Evidence (quote from customer interview):** "[verbatim]"
---
### 3. Product name
**Your product name:** [...]
---
### 4. Product category
**Bad (vague):** "platform", "solution", "tool"
**Good (specific):** "payment-data reconciliation platform", "developer-first observability tool", "AI-powered customer support automation"
The category should be one a customer would search for. If no one searches for "your category", you have either invented it (good if you can lead it) or hidden in it (bad -- harder to find).
**Your product category:** [...]
---
### 5. Statement of key benefit
**Bad (generic):** "saves time", "improves productivity"
**Good (specific):** "delivers a 2-day close with full audit traceability", "reduces incident MTTR from 45 minutes to 5 minutes"
The benefit should be quantified, customer-outcome-oriented, and tied to the need.
**Your statement of key benefit:** [...]
---
### 6. Primary competitive alternative
**Bad (generic):** "other tools", "the status quo"
**Good (specific):** "spreadsheet-based reconciliation", "Datadog + PagerDuty", "Zendesk Macros"
The alternative should be the *real* alternative -- the one most customers would use if your product did not exist. For most products, the alternative is *not* a competitor SaaS -- it is a spreadsheet, an internal tool, or human labor.
**Your primary competitive alternative:** [...]
---
### 7. Primary differentiation
**Bad (generic):** "easier to use", "better experience", "more features"
**Good (specific):** "produces an audit-ready trail automatically and scales to 100K transactions per close", "explains every alert with code-level context", "integrates with every payment processor, not just one"
The differentiation should be one thing -- the *primary* one. If you list five differentiators, you do not have one.
**Your primary differentiation:** [...]
---
## Assembled Pitch
[Write out the full pitch using your six answers]
---
## Test the pitch
### Test 1: Specificity
Read the pitch aloud. For each blank, ask: "could a competitor use this exact phrasing?" If yes, sharpen.
### Test 2: Memorability
Read the pitch once. Wait 1 minute. Try to repeat it. If you cannot, it is too long or too jargon-heavy.
### Test 3: Customer reaction
Show the pitch to 3 prospects. The response should be one of:
- "Yes, that's me." (Strong target fit)
- "No, that's not me." (Out-of-segment -- which is fine, the pitch is doing its job)
- "I don't understand." (BAD -- the pitch is unclear; rewrite)
If the response is "interesting, tell me more" without "that's me", the pitch is not yet activating.
### Test 4: Differentiation
Replace your product name with a competitor's name. Does the pitch still make sense? If yes, the differentiation is not yet sharp.
---
## Approval log
| Stakeholder | Date | Status | Notes |
|--------------|------|--------|-------|
| [PM] | [...] | Approved | |
| [Marketing lead] | [...] | Approved | |
| [Sales lead] | [...] | Approved | |
| [Exec sponsor] | [...] | Approved | |
**Locked version:** v[X.Y] as of [YYYY-MM-DD]
**Next review:** [YYYY-MM-DD] (typically annual or after major pivot)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |