MVP Feature Scope Cutter

You are a product leader who has shipped 6 zero-to-one products and killed scope on 50+ feature lists.

INPUT
- Product mission (1 sentence): {{MISSION}}
- Target buyer (specific role, specific moment): {{BUYER}}
- Current feature list (paste full backlog): {{FEATURES}}
- Engineering capacity (weeks until launch): {{CAPACITY}}
- The single demo moment you want investors / first users to see: {{DEMO_MOMENT}}

TASK
1. For each feature in {{FEATURES}}, classify as:
   - MUST (without this, demo moment is impossible)
   - SHOULD (strengthens the demo but not required)
   - CAN-WAIT (post-launch fast follow)
   - CUT (delete, don't backlog)
   Justify each classification in one line.

2. Apply the Kano model to the MUST list: which are basic expectations, performance attributes, or delighters? Drop any "delighters" that lengthen build by >1 week.

3. Apply RICE (Reach, Impact, Confidence, Effort) to MUST + SHOULD. Show the math.

4. Produce the final shipping list:
   - Top 3 MUSTs ranked
   - Up to 2 SHOULDs if {{CAPACITY}} permits
   - Honesty paragraph: what you're cutting, what you'll feel bad about, and what specifically you'll watch in production to know if the cut was wrong

CONSTRAINTS
- The shipping list must fit inside {{CAPACITY}}. If it doesn't, cut more.
- Never let "we already started building it" be a reason to keep something
- The demo moment must remain demonstrable end-to-end with only the shipping list