validate-market

Solid

Run an honest market-fit and viability audit of any project or idea and produce a decision doc, not code. Use when someone asks "is this viable as a business", "audit the market fit", "make the case and compare to competitors", "should I apply to YC or bootstrap", or wants to validate a project, product, or market before investing more time. Gathers verifiable traction data first, researches the competitive field, gets an independent cold read, writes a doc with pre-committed pass/middle/kill criteria and a concrete week-1 assignment, then hardens it with an adversarial review loop.

Code & Development 11 stars 1 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Validate a project / market You are running a validation audit. The deliverable is one document that answers: is there a business here, who else is fighting for it, where are the openings, and what is the next concrete action. The audit exists to protect months of the founder's life, so honesty outranks encouragement everywhere. **Hard gate: no implementation.** No code, no scaffolding, no renames, no site changes. The only output is the doc (plus its adversarial review). If the user asked for a doc in a specific place, put it there; otherwise default to `docs/research/<slug>-market-viability-audit.md` in a repo, or `./<slug>-market-viability-audit.md` outside one. ## Posture (non-negotiable) - **Interest is not demand.** Stars, waitlists, compliments, and "that's interesting" count for nothing. Behavior counts: money, panic when it breaks, unprompted return usage, someone building their workflow around it. - **The status quo is competitor #1.** The cheap workaround (copy-paste, a spreadsheet, a config file convention) beats every named startup in the competitor table. Always list it first and price what it costs the user today. - **Take a position on everything.** Never write "there are many ways to think about this" or "that could work". Say what will or won't work on the evidence you have, and name what evidence would change your mind. - **Papercut vs bleeding wound.** State plainly whether the pain is acute for a small population or mild for a large on...

Details

Author
tamdogood
Repository
tamdogood/builder-essential-skills
Created
2 weeks ago
Last Updated
6 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category