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.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add batterfried-philosophy172/Agent-Startup-Skills --skill mvp-scoper --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mvp Scoper?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/batterfried-philosophy172-mvp-scoper)More formats (shields.io, HTML) on the badges page.
---
name: mvp-scoper
description: >
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.
---
# 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:
1. **MVP (v1):** The 5-7 features that ship on day one
2. **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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!