validate-idea
Skill1 starsChanged 5 months agoMITView on GitHub
Pressure-test a SaaS idea before any PRD: problem, target user, market, willingness to pay. Run right after /start. Produces an idea-validation doc and a PROCEED/PIVOT/KILL verdict.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- insight68/Skillstheir own version, first seen Nov 8, 2026
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- sanskarprajapati/validator-skilltheir own version, first seen Nov 1, 2026
- alexjmiller5/agent-config-publictheir own version, first seen Oct 15, 2026
- scaccogatto/minimalist-entrepreneurtheir own version, first seen Oct 15, 2026
- menkesu/awesome-pm-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use company-values, find-community and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
insight68Skillcompany-values
Help define company values and culture for a minimalist business. Use when someone is setting up their company culture, preparing to hire, or wanting to codify what their company stands for.
Also in 6 projects that use this
insight68Skillfind-community
Help identify and evaluate communities to build a minimalist business around. Use when someone is looking for a business idea, trying to find their community, or wondering where to start as an entrepreneur.
Also in 6 projects that use this
slavingiaSkillgrow-sustainably
Evaluate business decisions through the lens of sustainable, profitable growth. Use when someone is making decisions about spending, hiring, fundraising, or scaling their business.
Also in 6 projects that use this
slavingiaSkillprocessize
Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.
Also in 6 projects that use this
MicrosoftSkilllaunch
Launch and automate VS Code Insiders with the Copilot Chat extension using @playwright/cli via Chrome DevTools Protocol. Use when you need to interact with the VS Code UI, automate the chat panel, test the extension UI, or take screenshots. Triggers include 'automate VS Code', 'interact with chat', 'test the UI', 'take a screenshot', 'launch with debugging'.
Also in 3 projects that use this
- +4 more from insight68
- +1 more from slavingia
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- slavingia/skills★ 11ksame name
- emotixco/claude-skills-founder★ 796same name
- me2resh/apexyard★ 542same name
- menkesu/awesome-pm-skills★ 441same name
- sendaifun/solana-new★ 178same name
- konglong87/superPM★ 84same name
- keeea/minimalist-entrepreneur-skills★ 19same name
- ariadoss/superskills★ 12same name
- lalulali/vespyr★ 11same name
- Latifox/find-me-saas★ 10same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- build-featureSkill
- code-reviewSkill
- compliance-checkSkill
- design-architectureSkill
- design-pricingSkill
- design-schemaSkill
- design-uiSkill
- helpSkill
- launch-checklistSkill
- map-flowsSkill
- qa-planSkill
- scope-checkSkill
- security-auditSkill
- setup-billingSkill
- setup-deploySkill
- setup-stackSkill
- startSkill
- studio-statusSkill
- test-setupSkill
- threat-modelSkill
- write-prdSkill
- write-testsSkill
The file
Files
Validate that a SaaS idea is worth building before investing in specs and code. Non-autonomous: ask first, present options, get sign-off.
Phases
- Frame the bet — restate the idea as: target user, problem, and the painful status quo. Confirm with the user.
- Probe demand — who pays, how much, what they use today, why they'd switch. Ask one question at a time.
- Assess fit & moat — why this team/stack, what's defensible, what's the riskiest assumption.
- Draft the canvas — fill
.claude/templates/idea-validation.mdintodocs/specs/idea-validation.md(draft, await approval). Honor the review intensity: underfull, walk through each canvas section for sign-off; underlean, get a single confirmation before writing; undersolo, proceed and summarize after. - Director gate — product-director gives a PROCEED / PIVOT / KILL verdict with the single biggest risk to de-risk next.
- Next step — on PROCEED, point to
/write-prd.
Output
docs/specs/idea-validation.md + a clear verdict. Writes nothing else without approval.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

