home / skills / eddiebe147 / claude-settings / mvp-planner

mvp-planner skill

/skills/mvp-planner

This skill helps plan minimum viable products by prioritizing features, aligning objectives, and guiding execution from discovery to optimization.

npx playbooks add skill eddiebe147/claude-settings --skill mvp-planner

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.3 KB
---
name: MVP Planner
slug: mvp-planner
description: Scope and plan minimum viable products with feature prioritization
category: business
complexity: simple
version: "1.0.0"
author: "ID8Labs"
triggers:
  - "mvp planning"
  - "minimum viable product"
  - "scope mvp"
  - "mvp features"
  - "mvp strategy"
tags:
  - mvp
  - planning
  - product
  - scope
  - features
---

# MVP Planner

Scope and plan minimum viable products with feature prioritization

## When to Use This Skill

Use this skill when you need to:
- Improve business operations and strategy
- Make data-driven business decisions
- Optimize processes and outcomes

**Not recommended for:**
- Tasks requiring creative design work
- technical coding

## Quick Reference

| Action | Command/Trigger |
|--------|-----------------|
| Create mvp planner | `mvp planning` |
| Review and optimize | `review mvp planner` |
| Get best practices | `mvp planner best practices` |

## Core Workflows

### Workflow 1: Initial MVP Planner Creation

**Goal:** Create a high-quality mvp planner from scratch

**Steps:**
1. **Discovery** - Understand requirements and objectives
2. **Planning** - Develop strategy and approach
3. **Execution** - Implement the plan
4. **Review** - Evaluate results and iterate
5. **Optimization** - Refine based on feedback

### Workflow 2: Advanced MVP Planner Optimization

**Goal:** Refine and optimize existing mvp planner for better results

**Steps:**
1. **Research** - Gather relevant information
2. **Analysis** - Evaluate options and approaches
3. **Decision** - Choose the best path forward
4. **Implementation** - Execute with precision
5. **Measurement** - Track success metrics

## Best Practices

1. **Start with Clear Objectives**
   Define what success looks like before beginning work.

2. **Follow Industry Standards**
   Leverage proven frameworks and best practices in business.

3. **Iterate Based on Feedback**
   Continuously improve based on results and user input.

4. **Document Your Process**
   Keep track of decisions and outcomes for future reference.

5. **Focus on Quality**
   Prioritize excellence over speed, especially in early iterations.

## Checklist

Before considering your work complete:

- [ ] Objectives clearly defined and understood
- [ ] Research and discovery phase completed
- [ ] Strategy or plan documented
- [ ] Implementation matches requirements
- [ ] Quality standards met
- [ ] Stakeholders informed and aligned
- [ ] Results measured against goals
- [ ] Documentation updated
- [ ] Feedback collected
- [ ] Next steps identified

## Common Mistakes

| Mistake | Why It's Bad | Better Approach |
|---------|--------------|-----------------|
| Skipping research | Leads to misaligned solutions | Invest time in understanding context |
| Ignoring best practices | Reinventing the wheel | Study successful examples first |
| No clear metrics | Can't measure success | Define KPIs upfront |

## Integration Points

- **Tools**: Integration with common business platforms and tools
- **Workflows**: Fits into existing business operations workflows
- **Team**: Collaborates with leadership and operations stakeholders

## Success Metrics

Track these metrics to measure effectiveness:
- Quality of output
- Time to completion
- Stakeholder satisfaction
- Impact on business goals
- Reusability of approach

---

*This skill is part of the ID8Labs Skills Marketplace. Last updated: 2026-01-07*

Overview

This skill scopes and plans minimum viable products with a focus on feature prioritization and measurable outcomes. It guides teams through discovery, planning, execution, review, and optimization to deliver a focused MVP that validates business assumptions. The skill is designed for product managers, founders, and operations leads who need a structured, repeatable MVP process.

How this skill works

The skill walks you through a staged workflow: discovery to capture objectives and constraints, planning to prioritize features and define success metrics, execution guidance to keep development focused, and review cycles to gather feedback and iterate. It inspects requirements, proposed features, KPIs, and stakeholder alignment to recommend a prioritized backlog and next steps. It also provides optimization techniques and checklists to ensure quality and measurable progress.

When to use it

  • Launching a new product or feature to validate market fit quickly
  • Creating a prioritized, resource-aware roadmap for early releases
  • Aligning stakeholders around clear MVP objectives and metrics
  • Improving business processes and decision-making with data-driven plans
  • Refining an existing MVP based on user feedback and metrics

Best practices

  • Define clear success criteria and KPIs before scoping features
  • Prioritize ruthlessly: focus on the smallest set of features that prove the hypothesis
  • Document decisions and assumptions for future iteration and learning
  • Run short review cycles and collect user feedback early
  • Use proven frameworks (e.g., RICE, MoSCoW) to score and prioritize features

Example use cases

  • A founder needs a 6-week plan to validate demand for a new SaaS feature
  • A product manager builds a prioritized backlog for a first public release
  • An operations lead standardizes MVP reviews across multiple teams
  • A team iterates an existing MVP after initial user testing and metrics
  • A business analyst defines KPIs and measurement approach for an experiment

FAQ

Is this skill suitable for detailed technical implementation or coding?

No. The skill focuses on scoping, prioritization, and planning rather than hands-on technical design or coding.

What inputs do I need to get started?

Provide business objectives, target user problems, constraints (time/budget), and any existing research or metrics to accelerate discovery.