Skip to main content
skill CX Codex

mvp-scope — Claude Code skill: what it does and how to install

The mvp-scope Claude Code skill turns a feature wishlist into a focused MVP plan. It kicks in when a founder needs to choose what to build first.

MIT ★ 900 updated 2026-11-03

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add emotixco/claude-skills-founder --skill mvp-scope -a claude-code
Open on GitHub

What mvp-scope does

mvp-scope sorts proposed features into must-have, should-have, and deferred groups. It states the MVP in a sentence, maps the key route from signup to user value, and lists features that can wait.

For the selected scope, the skill suggests a simple tech stack and separates custom work from services such as authentication, payments, or email. It estimates build time for one full-stack developer and suggests hosting options, with a check of current free-tier limits. The time estimates are for a solo developer, not an agency.

It reads founder/facts.md, founder/product-brief.md, founder/persona-gen.md, and founder/validate-idea.md, then saves the plan to founder/mvp-scope.md. The product idea and desired feature list are needed. It also reads ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md.

What it helps with

  • sort a feature wishlist by priority
  • define the smallest useful product release
  • map the user's route to the core value
  • estimate solo development time for an MVP
  • set launch checks for the first release

Example prompts for the agent

  • Turn this product idea and feature list into an MVP plan, then save it to founder/mvp-scope.md.
  • Help me decide what to build first from this product idea and its proposed features.

How to install mvp-scope

1Skills CLI (Vercel)

npx skills add emotixco/claude-skills-founder --skill mvp-scope -a claude-code

2Manually: put the files in place

~/.claude/skills/mvp-scope/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/mvp-scope/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about mvp-scope

How do I install mvp-scope in Claude Code?

Run npx skills add emotixco/claude-skills-founder --skill mvp-scope -a claude-code. The skill file is at ~/.claude/skills/mvp-scope/SKILL.md.

What does mvp-scope do?

It prioritizes proposed features, defines an MVP, maps the main user flow, and drafts a technical scope with build-time estimates. The plan is saved to founder/mvp-scope.md.

What does mvp-scope need to work?

It needs a product idea and the features being considered. It also reads files in founder and ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md.

Source text

SKILL.md · MIT
---
name: mvp-scope
description: 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.
argument-hint: "[your product idea and feature wishlist]"
allowed-tools: Read Edit(founder/**)
---

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.

© emotixco · MIT · emotixco/claude-skills-founder

Similar skills

All skills for Finance and business →

From the same set14

The whole set →
product-brief This Claude Code skill turns a startup concept into a structured product brief. It covers the problem, intended audience, product value, and an initial go-to-market plan. CX Codex +1 ★ 900repo stars pricing-strategy The pricing-strategy Claude Code skill develops product pricing and plan structures. It runs when a founder needs to set prices or decide what each plan includes. CX Codex +1 ★ 900repo stars pitch-deck The pitch-deck Claude Code skill outlines an investor presentation. It activates for a fundraising deck or a single slide on traction, market size, or competitors. CX Codex +1 ★ 900repo stars persona-gen The persona-gen Claude Code skill builds user personas to clarify or choose a product’s audience. It produces three profiles and a priority matrix to guide which group to build for first. CX Codex +1 ★ 900repo stars metrics-dashboard The metrics-dashboard Claude Code skill selects startup metrics and builds a tracking plan. It activates when a founder asks what to measure or how to report results to investors. CX Codex +1 ★ 900repo stars landing-page This Claude Code skill drafts landing page copy from the hero section through the final call to action. It runs when creating a page for a new or existing product. CX Codex +1 ★ 900repo stars go-to-market The go-to-market Claude Code skill plans a product launch and audience growth. It covers pre-launch preparation, launch-day tactics, and the first 90 days. CX Codex +1 ★ 900repo stars fundraise-prep The fundraise-prep Claude Code skill assesses startup readiness for a funding round. It helps size the raise, choose an instrument, and map investor outreach across 12 weeks. CX Codex +1 ★ 900repo stars

Project sponsors

Companies that keep this analytics open