Mvp scoper

Skill batterfried-philosophy172/Agent-Startup-Skills/skills/mvp-scoper

Build SaaS products using an 8-phase AI agent pipeline with mandatory approval gates for Antigravity, Claude Code, and Codex.

Install

npx -y skills add batterfried-philosophy172/Agent-Startup-Skills --skill mvp-scoper

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 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

Product scoping agent that cuts feature bloat and defines the minimum viable product. Triggers on: MVP scope, feature prioritization, what to build first, scope the product, feature list, v1 features.

SKILL.md

1.8 KB, as published. Nobody here has run it

MVP Scoper — Feature Prioritization Agent

Purpose

Prevent scope creep and feature bloat by ruthlessly prioritizing the smallest set of features that delivers value to the target user.

When to Use

After market research is approved
When the user has a long list of desired features
When the user says "what should I build first?"

Process

Step 1: Dream List

Ask the user to list EVERYTHING they want the product to do. No limits.

Step 2: The Cut

Apply the ICE framework to each feature:

Impact (1-10): How much does this move the needle for the user?
Confidence (1-10): How sure are we this is needed?
Ease (1-10): How easy is this to build?

Score = (Impact × Confidence × Ease). Rank all features.

Step 3: The MVP Line

Draw a hard line at the top 5-7 features. Everything below is "v2 backlog."

Present two lists:

MVP (v1): The 5-7 features that ship on day one
Backlog (v2+): Everything else, ranked by ICE score

Step 4: Success Metrics

Define 2-3 measurable success criteria for the MVP:

e.g., "A new user can complete the core action within 2 minutes"
e.g., "The app loads in under 3 seconds"

Step 5: Complexity Estimate

For each MVP feature, assign: Low / Medium / High complexity.

Output

Produce a mvp_scope.md file with:

Prioritized MVP feature list
v2 backlog
Success metrics
Complexity estimates

Exit Criteria

MVP has no more than 7 features
Each feature has a clear, one-sentence description
Success metrics are defined and measurable
Backlog exists for cut features