← ClaudeAtlas

mvp-scopinglisted

Define the smallest product that tests the riskiest assumption: the one job it must do, the type of MVP, a story map with a clear cut line, features sorted with the Kano model, what to fake or do by hand, a success criterion and a build plan in weeks. Use when a founder is about to build a first version, has a long feature list, or asks what an MVP should include. Triggers: "MVP", "minimum viable product", "first version", "feature list", "prioritize features", "produit minimum viable", "première version", "prioriser les fonctionnalités", "producto mínimo viable", "primera versión", "priorizar funcionalidades".
teodstr/garage · ★ 0 · AI & Automation · score 66
Install: claude install-skill teodstr/garage
# MVP scoping An MVP exists to learn, as cheaply as possible, whether customers want something. This skill cuts a feature list down to what the riskiest assumption requires, and finds what can be faked or done by hand. ## When to use - After the problem is validated (`customer-interviews`, `idea-validation`) and before building. - When the feature list keeps growing and the launch keeps moving. - Not for technical architecture or choosing a tech stack. ## Inputs 1. The riskiest assumption to test. 2. The target customer and the job the product does for them. 3. The feature wish list. 4. The team's skills, budget and weekly hours. ## Method 1. **Write the one job** the MVP does for one type of customer, in one sentence. 2. **Choose the type of MVP** that tests the assumption at the lowest cost: concierge (the service is done by hand for a few customers), Wizard of Oz (customers see a product, people do the work behind it), single-feature product, no-code or spreadsheet version, landing page with pre-orders (`landing-page`), clickable prototype (`prototype-testing`). 3. **Draw a story map** (Patton): the steps of the user's journey from left to right, the features under each step, and a cut line. Above the line goes only what the user needs to complete the journey once. 4. **Sort the features with the Kano model**: must-be (expected; their absence makes users unhappy), one-dimensional (the more, the better), attractive (delight that nobody expected), indifferent. The MVP