Mvp Scope logo

Mvp Scope

Organization
emotixco
mvp-scope

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.

Overview

Publisheremotixco
Repositoryclaude-skills-founder
Skill namemvp-scope
Stars
566
Forks
44
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by emotixco on GitHub. Read the source before you install it.

Installation

Install the Mvp Scope AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/emotixco/claude-skills-founder/tree/main/skills/mvp-scope
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/emotixco/claude-skills-founder.git /tmp/claude-skills-founder
mkdir -p .claude/skills
cp -r /tmp/claude-skills-founder/skills/mvp-scope .claude/skills/mvp-scope
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mvp Scope in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mvp Scope on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mvp Scope is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

FeatureCategoryReasoning
...Must have / Should have / Won't haveOne 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.

Frequently asked questions

What does the Mvp Scope AI skill do?

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.

Why use Mvp Scope on TypingMind?

Because you install it once and use it with any model. Mvp Scope is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mvp Scope in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/emotixco/claude-skills-founder/tree/main/skills/mvp-scope. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Mvp Scope?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mvp Scope?

As many as you like. As long as a model supports skills, you can use Mvp Scope with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mvp Scope AI skill free?

Yes. It is published on GitHub by emotixco under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇