
Idea Validator
- 252 installs
- 31 repo stars
- Updated August 2, 2026
- shipshitdev/library
idea-validator is an agent skill that scores startup concepts with the Hexa Opportunity Memo framework and an 8-rating Perceived Created Value scale from 0-24 for developers deciding whether to prototype a product idea.
About
idea-validator is a shipshitdev/library agent skill that rigorously assesses product ideas before engineering starts. It combines a Hexa Opportunity Memo assessment with Perceived Created Value scoring across four dimensions—price, quality, performance, and convenience—each rated for current problem severity and proposed improvement across eight total ratings summed from 0 to 24. Developers reach for idea-validator when they ask should I pursue this, propose a new build, or want to know if an idea is worth building. Score bands guide next steps: 0-6 weak, 7-12 needs refinement, 13-18 strong, 19-24 exceptional. The skill pairs with follow-on skills like market-sizer, startup-icp-definer, and mvp-architect after validation passes.
- Problem-solution fit scoring
- Audience and wedge definition
- Competitive gap review
- MVP boundary framing
- Explicit go/no-go criteria
Idea Validator by the numbers
- 252 all-time installs (skills.sh)
- +2 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #953 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/shipshitdev/library --skill idea-validatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 252 |
|---|---|
| repo stars | ★ 31 |
| Last updated | August 2, 2026 |
| Repository | shipshitdev/library ↗ |
How do you validate a product idea before building?
Stress-test a product idea for problem clarity, audience fit, differentiation, and feasibility before prototyping, landing tests, or writing a full PRD.
Who is it for?
Developers evaluating a new SaaS or product concept who need a structured go/no-go score before writing code or a full PRD.
Skip if: Skip idea-validator when the product is already in active development and you need implementation architecture or code review instead of concept scoring.
When should I use this skill?
The user proposes a new product idea, asks if it is worth building, or says should I pursue this without a validated scope.
What you get
Opportunity Memo assessment with 0-24 PCV score, interpretation band, and pursue-or-refine recommendation
- PCV score report
- Opportunity Memo assessment
By the numbers
- PCV scoring uses 8 ratings summed from 0 to 24
- Covers 4 dimensions: price, quality, performance, convenience
Files
Idea Validator - Startup Idea Assessment Framework
Rigorously assess startup ideas BEFORE building using structured validation—saving months of wasted effort on ideas that won't work.
Hexa's Principle: "You want to make something people want. But people don't always know what they want—so you need to understand what they actually need."
When This Activates
- User asks "is this a good idea"
- User says "I want to build X" without validation
- User asks "should I pursue this"
- User mentions a startup idea they're considering
- User wants to know if their idea is worth building
The Framework
Validation = Opportunity Memo Assessment + Perceived Created Value (PCV) Score
Problem Assessment Matrix
| Dimension | Rating | Impact |
|---|---|---|
| Frequency | [Daily/Weekly/Monthly] | High/Med/Low |
| Severity | [Critical/Important/Nice-to-have] | High/Med/Low |
| Awareness | [Actively seeking/Aware/Unaware] | High/Med/Low |
| Budget | [Has budget/Would find/No budget] | High/Med/Low |
Problem Score: 3-4 High = Strong. 1-2 = Weak. 0 = Not a real problem.
PCV Scoring (4 Dimensions)
Rate current solution problems + your improvement:
| Dimension | Current Problem | Your Improvement |
|---|---|---|
| Price | Not a problem / A problem / Serious | No diff / Some / Serious |
| Quality | Not a problem / A problem / Serious | No diff / Some / Serious |
| Performance | Not a problem / A problem / Serious | No diff / Some / Serious |
| Convenience | Not a problem / A problem / Serious | No diff / Some / Serious |
Scoring: a=0, b=1, c=3 points. Sum all 8 ratings.
| Score | Interpretation | Recommendation |
|---|---|---|
| 0-6 | Weak | Don't pursue |
| 7-12 | Moderate | Needs refinement |
| 13-18 | Strong | Worth pursuing |
| 19-24 | Exceptional | Build NOW |
Quick Discovery Questions
Problem Space:
1. What specific pain point does your ICP feel? 2. How do they currently solve this? 3. What's wrong with current solutions? 4. How often do they experience this pain? 5. What does this problem cost them?
Timing:
1. Why is NOW the right time? 2. What has changed recently? 3. What barriers existed before that are now gone?
ICP:
1. Company type, size, industry 2. Buyer vs. user role 3. What triggers them to seek a solution?
Integration
| Skill | When to Use |
|---|---|
market-sizer | After validation passes |
startup-icp-definer | Deep dive on customer |
mvp-architect | Scope the build |
leads-researcher | Find design partners |
---
For detailed execution workflow, output templates, and PCV calculations: references/full-guide.md
{
"name": "idea-validator",
"version": "1.0.0",
"description": "Use this skill when users need to validate a startup idea, assess problem-solution fit, evaluate mar",
"author": {
"name": "Ship Shit Dev",
"email": "hello@shipshit.dev",
"url": "https://github.com/shipshitdev"
},
"license": "MIT",
"skills": "."
}
Idea Validator - Full Guide
Complete guide to validating startup ideas using Hexa's Opportunity Memo framework and PCV methodology.
Step 1: Project Canvas (Executive Summary)
Ask the user:
Describe your idea in one sentence:
>
1. What problem are you solving?
2. Who has this problem?
3. What's your proposed solution?
4. Why you? (Why are you the right person to build this?)
One-Liner Template: "For [target customer] who [pain point], [Product Name] provides [solution] that [key benefit], unlike [alternatives] which [limitation]."
Step 2: Problem Space Deep Dive
Ask the user:
Tell me about the problem:
>
1. What is the specific pain point(s) your ICP feels?
2. How do they currently solve this problem?
3. What's wrong with the current solutions?
4. How often do they experience this pain?
5. What does this problem cost them?
Problem Assessment Matrix:
| Dimension | Current State | Impact |
|---|---|---|
| Frequency | [Daily/Weekly/Monthly/Yearly] | [High/Med/Low] |
| Severity | [Critical/Important/Nice-to-have] | [High/Med/Low] |
| Awareness | [Actively seeking/Aware/Unaware] | [High/Med/Low] |
| Budget | [Has budget/Would find budget/No budget] | [High/Med/Low] |
Problem Score: Count "High" ratings. 3-4 = Strong problem. 1-2 = Weak problem. 0 = Not a real problem.
Step 3: Context & Timing Analysis
Ask the user:
Why is NOW the right time for this solution?
>
1. What has changed recently that makes this possible/necessary?
2. What barriers existed before that are now gone?
3. What trends support this idea?
4. Why hasn't this been solved before?
5. What happens if they DON'T solve this in the next 12 months?
Timing Assessment:
| Factor | Evidence |
|---|---|
| Technology enablers | [What tech now exists?] |
| Market shifts | [What behavior has changed?] |
| Regulatory changes | [What's now allowed/required?] |
| Economic factors | [What budget/spending has shifted?] |
| Competitive vacuum | [Why hasn't this been built?] |
Step 4: ICP Definition
ICP Canvas:
┌─────────────────────────────────────────────────┐
│ IDEAL CUSTOMER PROFILE │
├─────────────────────────────────────────────────┤
│ Company: [Type, Size, Industry] │
│ Buyer: [Title, Role, Decision Authority] │
│ User: [Title, Daily workflow] │
│ Trigger: [What event creates urgency] │
│ Budget: [Who pays, typical spend range] │
│ Buying Center: [Who else influences decision] │
└─────────────────────────────────────────────────┘Step 5: Solution & Value Proposition
Value Proposition Framework:
| Element | Your Answer |
|---|---|
| For | [ICP description] |
| Who | [Key pain point] |
| Our product is | [Category] |
| That provides | [Key benefit] |
| Unlike | [Primary alternative] |
| We | [Key differentiator] |
Step 6: Competitive Landscape
Competitive Analysis:
| Competitor | Type | Strengths | Weaknesses | Your Advantage |
|---|---|---|---|---|
| [Name] | Direct | |||
| [Name] | Indirect | |||
| DIY/Manual | Alternative | |||
| Status Quo | Inaction |
Step 7: Perceived Created Value (PCV) Scoring
Phase 1: Interview 20 potential customers
- Ask open-ended questions about their problem
- Understand their current solutions
- Don't pitch your solution—listen
Phase 2: Assess Current Solution
| Dimension | Definition | Rating |
|---|---|---|
| Price | Cost of current solution | [a] Not a problem / [b] A problem / [c] Serious problem |
| Quality | Relevance, reliability, service | [a/b/c] |
| Performance | Speed, output, efficiency | [a/b/c] |
| Convenience | Usability, accessibility, ease | [a/b/c] |
Phase 3: Evaluate Your Solution
| Dimension | Your Improvement |
|---|---|
| Price | [a] No difference / [b] Some improvement / [c] Serious improvement |
| Quality | [a/b/c] |
| Performance | [a/b/c] |
| Convenience | [a/b/c] |
Phase 4: Calculate PCV Score
Scoring: a=0 points, b=1 point, c=3 points
Sum all 8 ratings (4 problem + 4 solution):
| Score | Interpretation | Recommendation |
|---|---|---|
| 0-3 | Weak opportunity | Don't pursue |
| 4-6 | Moderate opportunity | Needs work—pivot or refine |
| 7-9 | Strong opportunity | Worth pursuing with caution |
| 10-12 | Excellent opportunity | Green light—move fast |
| 13+ | Exceptional opportunity | Build NOW |
Step 8: Design Partner Validation
Design Partner Readiness:
| Criteria | Status |
|---|---|
| 3-5 identified potential customers | [Yes/No] |
| They've agreed to test early versions | [Yes/No] |
| They'll commit to regular feedback calls | [Yes/No] |
| They'll pay something (even discounted) | [Yes/No] |
| They have the problem acutely | [Yes/No] |
Score: 4-5 = Ready to build. 2-3 = Need more validation. 0-1 = Not ready.
Output Template
# Idea Validation Report: [Idea Name]
## Executive Summary
**One-Liner:** [For X who Y, Product provides Z]
**PCV Score:** X/24
**Recommendation:** [Don't pursue / Needs work / Worth pursuing / Green light]
**Confidence Level:** [Low/Medium/High]
## Problem Assessment
### The Problem
[Description]
### Problem Score: X/4
| Dimension | Rating | Evidence |
|-----------|--------|----------|
| Frequency | [High/Med/Low] | [Why] |
| Severity | [High/Med/Low] | [Why] |
| Awareness | [High/Med/Low] | [Why] |
| Budget | [High/Med/Low] | [Why] |
## PCV Score Breakdown
### Current Solution Problems (Customer's Pain)
| Dimension | Rating | Points |
|-----------|--------|--------|
| Price | [a/b/c] | [0/1/3] |
| Quality | [a/b/c] | [0/1/3] |
| Performance | [a/b/c] | [0/1/3] |
| Convenience | [a/b/c] | [0/1/3] |
| **Subtotal** | | **X/12** |
### Your Solution Improvement
| Dimension | Rating | Points |
|-----------|--------|--------|
| Price | [a/b/c] | [0/1/3] |
| Quality | [a/b/c] | [0/1/3] |
| Performance | [a/b/c] | [0/1/3] |
| Convenience | [a/b/c] | [0/1/3] |
| **Subtotal** | | **X/12** |
### **Total PCV Score: X/24**
## Validation Next Steps
### If Score < 7
- [ ] Interview 10 more potential customers
- [ ] Identify what you got wrong about the problem
- [ ] Consider pivoting
### If Score 7-12
- [ ] Double down on customer interviews
- [ ] Refine value proposition
- [ ] Find 3 design partners before building
### If Score 13+
- [ ] Lock in 3-5 design partners
- [ ] Use `market-sizer` to size the opportunity
- [ ] Start building within 2 weeks
## Final Recommendation
**Verdict:** [Don't pursue / Pivot / Proceed with caution / Full speed ahead]
**If proceeding, first priority:** [Single most important next action]The 20-Interview Rule
Before declaring an idea validated:
1. Talk to 20 potential customers (not friends, not family) 2. Ask about their problem (not your solution) 3. Understand how they solve it today 4. Learn what they'd pay for a better solution 5. Get 3-5 to commit as design partners
If you can't find 20 people to interview, the market might not exist.
Common Mistakes to Avoid
1. Confirmation bias: Only talking to people who agree with you 2. Solution-first thinking: Falling in love with solution before validating problem 3. Fake validation: Counting "that's cool" as validation (it's not) 4. Too broad ICP: "Everyone" is not a customer segment 5. Skipping competition: Assuming no competition means opportunity 6. Ignoring timing: Good idea at wrong time = failed startup 7. No design partners: Building before anyone commits to use it 8. Vanity validation: Surveys instead of real conversations
Related skills
How it compares
Pick idea-validator over writing-prds when you need a scored go/no-go on the concept itself rather than a detailed requirements document.
FAQ
How does idea-validator score product ideas?
idea-validator scores ideas using eight Perceived Created Value ratings across price, quality, performance, and convenience dimensions, summed from 0 to 24 with bands at 0-6 weak, 7-12 moderate, 13-18 strong, and 19-24 exceptional.
What framework does idea-validator use?
idea-validator combines the Hexa Opportunity Memo assessment with Perceived Created Value methodology to evaluate problem-solution fit, market opportunity, and whether a concept merits prototyping or refinement.