MVP development toolkit using BMAD methodology. Transform ideas into working products through structured phases - product brief, technical spec, sprint planning, and iterative development. Optimized for vibe coding workflows.
View on GitHubplugins/mvp-builder/skills/mvp-builder/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/mralbertzwolle/vibe-coding-academy-tools/blob/main/plugins/mvp-builder/skills/mvp-builder/SKILL.md -a claude-code --skill mvp-builderInstallation paths:
.claude/skills/mvp-builder/# MVP Builder Skill This skill provides a complete MVP development workflow optimized for vibe coders. It adapts the BMAD (Business/Market → Architecture → Development) methodology for AI-assisted rapid development. ## Core Principles ### Vibe Coding MVP Philosophy 1. **Ship Fast** - Get something working in days, not months 2. **Validate Early** - User feedback > perfect code 3. **Iterate Quickly** - Small improvements, frequent releases 4. **Right-Size** - Match complexity to project size 5. **Stay Focused** - One core feature done well ### Project Sizing Automatically adjust process based on scope: | Level | Description | Timeline | Process | |-------|-------------|----------|---------| | 0 | Quick prototype | Hours | Brief → Build | | 1 | Weekend project | 1-3 days | Brief → Spec → Build | | 2 | Side project | 1-2 weeks | Full light process | | 3 | Serious product | 1-2 months | Full process | | 4 | Complex product | 3+ months | Extended process | ## Phase 1: Product Brief ### Structure ```markdown # Product Brief: [Name] ## Vision One sentence describing the product's purpose. ## Problem Statement - Who has this problem? - What is the problem? - How painful is it? (1-10) - Current solutions and their shortcomings ## Target User - Primary persona: [Name, role, context] - Key characteristics: [List] - Jobs to be done: [List] ## Core Value Proposition [One clear statement of unique value] ## MVP Scope ### Must Have (P0) - [ ] Feature 1 - [Why essential] - [ ] Feature 2 - [Why essential] ### Should Have (P1) - [ ] Feature 3 - [Value added] - [ ] Feature 4 - [Value added] ### Nice to Have (P2) - [ ] Feature 5 - [Future consideration] ## Success Metrics 1. [Metric 1] - Target: [Value] 2. [Metric 2] - Target: [Value] ## Constraints - Timeline: [Deadline] - Budget: [Amount] - Technical: [Limitations] - Team: [Resources] ## Assumptions to Validate 1. [Assumption] - How to test 2. [Assumption] - How to test ``` ### Brief Generation Process 1. Ask c