Mvp spec
A founder/indie-hacker skills pack for Claude Code, Cursor, Codex and Gemini CLI: market research, competitor analysis, outcome-based pricing, landing-page copy, MVP spec, cold outreach, growth experiments and fundraising narrative.
npx -y skills add Hayatelin/founder-skills --skill mvp-specAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turns a raw idea into a lean MVP spec: problem, goals/non-goals, core user flow, scope cut, and a single success metric. Trigger on "scope my MVP", "what should I build first", "MVP spec", "cut this to an MVP", or "turn my idea into a build plan".
SKILL.md
2.3 KB, as published. Nobody here has run it
When to use
When a founder has an idea (or a bloated feature list) and needs the smallest thing that proves the core value and can ship in 2-4 weeks.
Inputs to gather
- The idea in one sentence and the ICP.
- The single riskiest assumption that must be true for this to work.
- The one user outcome that, if delivered, proves value.
- Any hard constraints (time, budget, solo vs. team, existing tools).
Process
- State the problem sharply: who, in what situation, fails to do what today.
- Pick ONE core flow — the single path from trigger to value. Everything else waits.
- Goals / non-goals: list 2-3 goals and, crucially, 3-5 explicit non-goals (the features you are not building yet). Non-goals are where MVPs are won.
- Cut scope ruthlessly with the test: "Does the user reach the core outcome without this?" If yes, defer it. Fake the rest (manual ops, no-code, Wizard-of-Oz).
- Pick one success metric with a number and a deadline (e.g. "10 users complete the core flow and 3 say they'd pay, within 3 weeks").
- Moat seed: note what proprietary data or workflow lock-in this MVP starts accruing — so v1 isn't a disposable thin wrapper.
Output
- Problem statement (1-2 sentences).
- Core user flow as numbered steps (trigger → action → value).
- Goals (2-3) and Non-goals (3-5, explicit).
- Scope cut list: in v1 vs. deferred, with the reason for each cut.
- Success metric: one number + one deadline.
- Riskiest-assumption test: the cheapest experiment that de-risks it before building.
Quality bar & pitfalls
- Good = a solo founder (or 2 people + AI) could ship it in 2-4 weeks and learn something real.
- An MVP tests the riskiest assumption, not "version 1.0 minus polish".
- Manual/concierge backends beat building automation you haven't validated.
- Avoid: scope creep disguised as "table stakes"; no success metric; building before the riskiest assumption is tested; shipping a thin wrapper with nothing proprietary started.