Below is a wish-list of features. Convert it into a scoped plan with these three sections:
1. MVP (ship by end of quarter): the smallest meaningful slice that delivers the core value. Maximum 5 items. If you need more than 5, force a cut and explain it.
2. Next increment (next quarter): items that should ship soon but don't fit the MVP. Maximum 5 items.
3. Explicitly out of scope (do not add back without a new decision): items dropped from the MVP, each with a one-line reason ('speculative', 'requires X infra', 'low signal from interviews', etc.).
End with a one-paragraph reasoning explaining why this slicing.
The wish-list:
{{wish_list}}
MVP definition from a wish-list
Add to PromptPaste
Download PromptPaste for MacDownload PromptPaste for iPhoneDownload PromptPaste for iPadDownload PromptPaste for Mac & iPhone
the prompt
Example output
Wish-list (15 items) → MVP scope:
MVP (ship by end of quarter):
1. Save filter state per user, restore on next session.
2. One-time in-app prompt for power users (>10 sessions) to enable.
3. Settings toggle to disable / clear saved filters.
Next increment (Q3):
4. Cross-device sync via iCloud (requires capacity confirmation).
5. 'Last 5 filter sets' history with one-tap restore.
6. Export filter set as a shareable link.
Increment after that (Q4 or later):
7. Filter sharing across teammates (requires permissions surface).
8. Filter analytics dashboard for admins.
Explicitly out of scope (do not add back without a new decision):
- Filter recommendations based on team usage (item 9 from wish-list) - requires ML infra we don't have.
- Filter version history / rollback (item 11) - low signal from interviews.
- Filter templates marketplace (item 14) - speculative; revisit after 2 quarters of usage data.
Reasoning: The MVP is the 80% case (single-user, single-device, the thing everyone asked for). Increments 4-6 unlock the second-most-cited need. Out-of-scope items are either infra-heavy or speculative.
Common mistakes
Don't accept an MVP scope that has more than 5 items. If the model returns a 7-item MVP, push back: 'cut to the smallest meaningful slice.' MVPs that ship are 2-4 items. Also: do not let the 'out of scope' section be a parking lot. Each out-of-scope item needs a one-line reason - 'speculative' or 'requires X infra' or 'low signal from interviews'. Without a reason, the items get re-added next planning cycle and you re-debate from scratch.
More from AI Prompts for Product Managers
PRD draft from a one-line problem
Act as a senior product manager. I'm going to give you a one-line problem statement. Before drafting any PRD, do this: 1. State the…
Customer interview synthesis
Read the raw customer interview transcripts below. Produce: 1. The top 5 themes ranked by frequency (number of interviews where the theme…
Stakeholder weekly update
Convert my raw bullets below into a weekly stakeholder update. Use exactly three sections: 1. Shipped: each item with a one-line outcome,…
Why it works
Wish-list-to-MVP is the single hardest scoping conversation in product. PMs end up either shipping the full wish-list (slow, scope-creep, missed window) or cutting too aggressively and missing the actual core (DOA launch). This prompt forces the discipline: paste a 10-30 item feature wish-list, get back the smallest meaningful slice that delivers the core value, plus the next two increments to ship later, plus an explicit 'out of scope' list. The 'out of scope' list is the differentiator - it makes the cut decisions visible so they can be debated rather than discovered six weeks in. Use this whenever a stakeholder hands you a wish-list and asks 'what can we ship by end of quarter?'. Tested cleanest on Claude Opus 4.7.