Skip to content
Skills Library
Management & product · Analysis

validate-idea

/validate-idea

Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.

Repository
superpowers ↗
Licence
MIT
Last repository change
15.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.

Original author description

Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.

How it works

  1. Core Principle
  2. The Minimalist Validation Process
  3. Red Flags (Do Not Build If...)
  4. Green Flags (Worth Pursuing If...)
  5. Output
Original SKILL.md headings · 65 lines, 500 words
SKILL.md preview
---
name: validate-idea
description: Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.
---

You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user validate their business idea before they write a single line of code or spend a dollar.

## Core Principle

**Validation happens through selling, not building.** Most founders spend months building a product nobody wants. Instead, validate by selling a manual version of your solution first.

## The Minimalist Validation Process

### Step 1: Define the Problem (not the solution)

Ask the user:
- Who specifically has this problem? (Be precise — not "businesses" but "freelance graphic designers who struggle with invoicing")
- How are they solving it today? (The current workaround is your real competition)
- How painful is this problem? (Mild annoyance vs. hair-on-fire)
- Would they pay to make this problem go away?

### Step 2: Can You Solve It Manually First?

Before building anything, can you solve this problem for people by hand?

- Sahil calls this **"processizing"** — creating a manual valuable process
- Do it yourself first. Hire yourself. Write down every step on a piece of paper
- If you can solve it manually for a few people, you can eventually automate it
- Example: Gumroad started as Sahil manually collecting PayPal info and paying creators one by one

### Step 3: Will People Pay?

The ultimate validation is a transaction. Ask:
- Can you charge for this manual service right now?
- Have you talked to at least 10 potential customers?
- Have at least 3 of them said they'd pay (or actually paid)?
- What price point feels natural?

### Step 4: Four Questions to Ask Before Building

From the book — ask yourself:
1. **Can I ship it in the span of a weekend?** First iteration should be prototyped in 2-3 days.
2. **Is it making my customers' life a little better?** That's a minimum viable product.
3. **Is a customer willing to pay me for it?** Profitable from day one.
4. **Can I get feedback quickly?** The faster the feedback loop, the faster you build something worth paying for.

## Red Flags (Do Not Build If...)

- Nobody is currently trying to solve this problem (no existing workarounds)
- You can't name 10 specific people who have this problem
- The only validation is "my friends think it's a cool idea"
- You need to educate people that they have this problem
- You're building for a community you don't belong to

## Green Flags (Worth Pursuing If...)

- People are already paying for inferior solutions
- You've manually solved this for a few people and they loved it
- The community is actively complaining about this problem
- You can describe the customer and their pain point in one sentence
- You're scratching your own itch

## Output

Give the user a clear verdict:
- **Validated**: Strong signals, proceed to MVP
- **Needs more validation**: Specific next steps to gather evidence
- **Pivot**: The idea needs fundamental changes — suggest directions

Versions

RepositoryScoreLicence
This page · LUNARTECH-X/superpowers100MIT
TerminalSkills/skills100Apache-2.0
sanskarprajapati/validator-skill100MIT
menkesu/awesome-pm-skills100MIT
pivyme/suiperpower100MIT
diegoaguilar2209/alexis90MIT

Identical content appears in 3 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 721e70d68df2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100validate
    Use this skill to test whether an idea is worth pursuing before building it, or to find an idea in the first place: 'is this a good idea,' 'should I build this,' 'pressure test my idea,' 'how do I know anyone wants this,' 'I don't have an idea yet,' 'do it by hand first,'…
  • 90ideas:refine
    This skill should be used when the user wants to sharpen, distill, or pressure-test an existing idea. Triggers include "refine this idea", "what's the core of this", "help me cut this down", "is this idea any good", "challenge this idea", "help me decide if this is worth…
  • 90idea-validation
    Test whether a proposed product or business is worth pursuing before major investment. Use to pressure-test a customer problem, alternatives, willingness to act and the cheapest meaningful validation experiment; not for building a full product or writing a generic business plan.
  • 90assess
    Use when someone wants to know whether an idea deserves building before anyone builds it: \"is this worth doing?\", \"should we build X?\", \"evaluate this idea\", \"would users actually want this?\", \"help me decide whether to invest in this\", a product or business idea with…
  • 90minimalist-review
    Review any business decision, plan, or strategy through the minimalist entrepreneur lens. Use when someone wants a gut-check on a business decision, wants to simplify their approach, or needs to decide between options.
  • 100propose
    Evaluate whether a software idea is worth building, then write the proposal document. Use when the user wants to assess an idea, says "evaluate", "propose", "is this worth building", or "should we build". If the idea passes evaluation, write the proposal document using the provided template.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.