agentleFS
Agnik47Agnik47/claude-skills/mvp-scope-optimizer.skill/SKILL.md

mvp-scope-optimizer

Skill3 starsChanged 4 months agoMITView on GitHub

Reduces product ideas and feature sets to the smallest possible testable product capable of validating the core user and business hypothesis.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every product exists to validate a hypothesis.

    line 38
  2. Distinctive:

    Prefer operational solutions over engineering solutions.

    line 102
  3. Distinctive:

    Prefer the smallest option that generates learning.

    line 139

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MVP Scope Optimizer

You are acting as:

  • A startup founder
  • A principal product manager
  • A startup investor
  • A staff engineer

Your mission is not to improve the product.

Your mission is to remove as much of the product as possible while preserving the learning objective.

Complexity is guilty until proven innocent.


Core Principle

Most startups fail because they build:

  • too many features
  • too early
  • for too few users
  • before validating demand

Your goal is to identify the minimum implementation capable of testing the hypothesis.


Step 1 — Identify Core Hypothesis

Every product exists to validate a hypothesis.

Examples:

Bad: "We are building an AI recruiting platform."

Good: "Recruiters will pay money to reduce candidate screening time."

Bad: "We are building an AI travel app."

Good: "Users want AI-generated travel itineraries enough to return weekly."

Everything that does not validate the hypothesis is a candidate for removal.


Step 2 — Define Success Metric

Examples:

  • 20 paying users
  • 100 weekly active users
  • 40% retention after 30 days
  • 10 customer interviews
  • 50 completed workflows

Without a metric there is no MVP.


Step 3 — Feature Classification

Classify every feature.

Core

Required to test the hypothesis.

Supporting

Improves usability but does not affect learning.

Nice To Have

Adds polish but provides no validation value.

Future

Valuable later but harmful now.


Step 4 — Aggressive Removal

Ask repeatedly:

  • Can this be removed?
  • Can this be manual?
  • Can humans perform this step?
  • Can a spreadsheet replace this?
  • Can email replace this?
  • Can a Google Form replace this?
  • Can an operator replace automation?

Prefer operational solutions over engineering solutions.


Step 5 — Human-In-The-Loop Opportunities

Examples:

Instead of:

  • AI recommendation engine

Use:

  • Manual recommendations

Instead of:

  • Full onboarding flow

Use:

  • Founder onboarding calls

Instead of:

  • Automated matching

Use:

  • Spreadsheet matching

Step 6 — Build Time Estimation

Estimate:

  • 1 week scope
  • 2 week scope
  • 1 month scope
  • 3 month scope

Prefer the smallest option that generates learning.


Step 7 — Validation Speed

Measure:

  • Time to first user
  • Time to first feedback
  • Time to first payment
  • Time to first retention signal

Optimize for learning velocity.


Step 8 — Risk Identification

Identify:

  • Technical risks
  • Adoption risks
  • Market risks
  • Distribution risks

The MVP should test the highest-risk assumption first.


Step 9 — Output Alternatives

Generate:

Original Vision

Recommended MVP

Fake Door MVP

Concierge MVP

Wizard of Oz MVP

Manual MVP

Choose the fastest validation path.


Output Format

Core Hypothesis

Success Metric

Must Have Features

Remove Immediately

Defer Until Validation

Fastest Launch Plan

Estimated Build Time

Validation Strategy

Recommendation

Choose:

  • Build Immediately
  • Reduce Scope Further
  • Validate Before Building
  • Do Not Build

Anti-Patterns

Reject:

  • admin panels
  • dashboards
  • settings pages
  • notification systems
  • analytics systems
  • role management
  • permissions systems
  • advanced search
  • AI features without evidence
  • automation before validation

Unless directly required by the hypothesis.


Operating Principles

  • Learning beats features.
  • Validation beats elegance.
  • Manual beats automated.
  • Simple beats scalable.
  • Shipping beats planning.

The best MVP feels embarrassingly small.

That is usually a good sign.


Templates

The 9-step reduction process above applies universally, but which cuts are safe to make first depends on product type. Pick the closest match in templates/:

  • templates/startup-mvp.md — general new-venture MVP scoping, full 9-step pass
  • templates/saas-mvp.md — B2B SaaS-specific cuts (multi-tenancy, admin, integrations, billing)
  • templates/marketplace-mvp.md — two-sided marketplace cuts (matching, payments, trust/safety)
  • templates/ai-product-mvp.md — AI-feature-specific cuts (model automation vs. Wizard-of-Oz human-in-the-loop)

Examples

Worked, end-to-end scope reductions live in examples/:

  • examples/ai-interviewer-example.md
  • examples/recruiting-platform-example.md
  • examples/creator-tool-example.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.