Cut scope down to a shippable v1

I am building {{product name}}. Here is everything I have thought of:
{{list every idea, one per line}}

My constraints: {{n}} people, and I want v1 live within {{timeframe}}.

Help me cut this to a minimum shippable version:
1. Sort every idea into three buckets: dead without it (must) / better with it (could) / overthinking (cut).
2. Justify each bucket, especially the cuts - say plainly why building it now is a waste.
3. Give me the v1 feature list, capped at {{target count, e.g. 3}} items.
4. Finally: after v1 ships, what will users complain about most?

Rules: do not be agreeable. Cut what must be cut. I want a version I can ship, not a fantasy feature set.

Replace the {{}} parts with your own content

Why it works

1. Forcing three buckets with reasons stops AI from hedging and marking everything "recommended"
2. Stating team size and deadline makes AI cut against real capacity, not infinite resources
3. "Do not be agreeable" measurably increases how hard AI cuts - it defaults to pleasing you
4. Asking for the top complaint up front surfaces the real cost of the MVP before launch, not after

What it looks like

For a party game, trimming "leaderboard, friend invites, custom decks, skin shop" down to just "draw a card + timer" to first validate whether anyone plays it at all.

Where it bites

• !Without team size and time, AI hands you a three-month plan, which is not a cut at all
• !Not recording what you cut, so you quietly add it back a few days later and loop forever

Browse categories