TechnicalCollectible prompt
MVP spec with core flow, screens and a cut list
Act as a product manager who has shipped many first versions. Write an MVP spec for {{app_idea}}, for {{target_audience}}. Features I have in mind: {{features}}. I'd like to launch by {{launch_date}}.
Include:
1. The problem, and the one outcome the MVP must prove, with a number that shows it worked
2. The riskiest assumption, and the cheapest way to test it, even by hand
3. The single core flow, step by step
4. Every feature sorted into Must have, Later or Never, with a reason for each cut
5. The fewest screens that support the core flow, and what each one shows
6. The main records to store, and who can see or change them
7. What to fake at first, such as manual work behind a simple form
8. Which payments, emails and integrations are needed now, and which can wait
9. A week-by-week plan to the launch date, with an honest warning if it's unrealistic
Be ruthless: version 1 should feel a little embarrassing. Finish with a short build brief I can paste into an AI app builder.
Ask me up to three questions first if the users or the problem are vague.
Technicalnvoka.com/library/nvoka-mvp-spec-for-your-app-ideaScan to open
Technical
MVP spec with core flow, screens and a cut list
Scope a first version you can build in weeks, with the core flow, screens, data and a cut list.
Curated by Nvoka
ClaudeChatGPTGemini
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 4 filledYour prompt
Act as a product manager who has shipped many first versions. Write an MVP spec for {{app_idea}}, for {{target_audience}}. Features I have in mind: {{features}}. I'd like to launch by {{launch_date}}.
Include:
1. The problem, and the one outcome the MVP must prove, with a number that shows it worked
2. The riskiest assumption, and the cheapest way to test it, even by hand
3. The single core flow, step by step
4. Every feature sorted into Must have, Later or Never, with a reason for each cut
5. The fewest screens that support the core flow, and what each one shows
6. The main records to store, and who can see or change them
7. What to fake at first, such as manual work behind a simple form
8. Which payments, emails and integrations are needed now, and which can wait
9. A week-by-week plan to the launch date, with an honest warning if it's unrealistic
Be ruthless: version 1 should feel a little embarrassing. Finish with a short build brief I can paste into an AI app builder.
Ask me up to three questions first if the users or the problem are vague.