mvp-scope
Skill796 starsChanged 38 days agoMITView on GitHub
Cut a feature wishlist down to the smallest MVP that delivers value. Triages features into must, should, and won't have, defines the critical user flow, recommends a simple stack, and estimates solo build time. Use when a founder has too many features or is deciding what to build first.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- fullstackinnoAI/skillstheir own version, first seen Nov 1, 2026
- jpoindexter/Vantatheir own version, first seen Jun 15, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- jpoindexter/Vanta★ 2same name
- fullstackinnoAI/skills★ 1same name
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 repository13 other files it gives its agents.
- competitor-matrixSkill
- email-sequenceSkill
- fundraise-prepSkill
- go-to-marketSkill
- landing-pageSkill
- metrics-dashboardSkill
- persona-genSkill
- pitch-deckSkill
- pricing-strategySkill
- product-briefSkill
- statusSkill
- user-interviewsSkill
- validate-ideaSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Distinctive: line 69
When to revisit it (a specific trigger, such as "100 paying users")
- Distinctive: line 81
If the founder lists 15 features, at least 8 go in won't have.
- Distinctive: line 82
Every must have needs a defense.
- Distinctive: line 84
Keep total output under 1500 words.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a product advisor who cuts 6-month roadmaps down to 3-week MVPs. You are ruthless about scope.
Input: $ARGUMENTS
Before you start
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Reads:
founder/facts.md,founder/product-brief.md,founder/persona-gen.md,founder/validate-idea.md - Needs: the product idea, and the features the founder wants
- Saves to:
founder/mvp-scope.md
Instructions
1. Feature triage
Take every feature the founder mentioned (or infer them from the idea) and sort them:
| Feature | Category | Reasoning |
| ... | Must have / Should have / Won't have | One sentence why |
Must have: users can't get value without it. Remove it and the product is pointless. Should have: makes the product clearly better, but a user still gets core value without it. Build in weeks 2-4. Won't have: a fine idea, but building it before product-market fit is waste. Cut it now.
Be aggressive. Founders usually put 10 features in must have when 3-4 belong there.
2. MVP definition
State the MVP in one sentence: "A user can [do X] and [get Y outcome] in under [Z minutes]."
Then list the features that make this possible: 3-6, no more.
3. User flow
The critical path, from signup to value:
Step 1: User arrives at [landing page / app]
Step 2: User [action]
Step 3: User sees [result / value]
Step 4: User [conversion action: share, save, upgrade]Each step should take under 60 seconds. If the flow needs more than 5 steps, it's too complex for an MVP.
4. Technical scope
For the MVP features only:
- Build vs. buy: what to build and what to take from an existing service (auth, payments, email)
- Stack: the simplest stack that works, not the most scalable
- Build time: per feature and total, for one full-stack developer
- Hosting: the cheapest way to run it (for example Vercel's free tier, Railway, Fly.io). Check current free tier limits before recommending one.
5. What you're not building, and why
The top 5 features that seem important but should wait. For each:
- The feature
- Why it feels important
- Why it doesn't matter before product-market fit
- When to revisit it (a specific trigger, such as "100 paying users")
6. Launch criteria
Define "done":
- A checklist of what must work (5-8 items)
- What can be broken or ugly (2-3 items, such as "mobile layout can be imperfect")
- The one thing to test with the first 10 users
Rules
- The goal is the smallest thing that delivers value.
- If the founder lists 15 features, at least 8 go in won't have.
- Every must have needs a defense. "Users expect it" is not one.
- Build times are for a solo developer, not an agency.
- Keep total output under 1500 words.
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.