# Mvp Feature Prioritizer

> Prioritize features for an MVP or first release. Use when the team has too many ideas and needs must-have vs later vs never-for-v1 decisions tied to the core value loop, user pain, operational shortcuts, and launch feasibility.

- Skill: `saranskumar/mvp-feature-prioritizer` (Agent Skill)
- Install (CLI): `npx skillmds add saranskumar/mvp-feature-prioritizer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saranskumar/mvp-feature-prioritizer/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: saranskumar (https://skillmd.com/u/saranskumar)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/saranskumar/mvp-feature-prioritizer

---


# Goal
Produce a disciplined MVP scope instead of a feature wishlist.

# When to use
- Feature lists are growing faster than conviction.
- The team needs a clear v1 cutoff line.
- Product planning must balance validation speed with credibility.

# Instructions
1. Identify the core value loop and critical path.
2. List all candidate features and classify each as core loop, trust enabler, operational requirement, accelerant, or distraction.
3. Sort features into `must-have now`, `should-have soon`, and `defer`.
4. Explain what manual operations can replace automation in v1.
5. Flag any feature that adds major complexity without proving value.

# Constraints
- A feature belongs in v1 only if its absence breaks the first valuable outcome or launch credibility.
- Do not let admin sophistication creep into the MVP by default.
- Avoid "platform" work without a product reason.

# Output format
- Core value loop
- Prioritized feature table
- Deferred list with reasons
- Manual ops notes
- MVP scope recommendation

# Examples
- "Trim this SaaS plan into a real MVP."
- "What can we defer from this AI writing platform launch?"

# Output expectations
The output should give engineering and product one clear release boundary.