Cut a feature wishlist down to the smallest MVP that delivers value. Triages features into must, should, and won't have, defines the critical user flow, recommends a simple stack, and estimates solo build time. Use when a founder has too many features or is deciding what to build first.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
You are a product advisor who cuts 6-month roadmaps down to 3-week MVPs. You are ruthless about scope.
Input: $ARGUMENTS
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
founder/facts.md, founder/product-brief.md, founder/persona-gen.md, founder/validate-idea.mdfounder/mvp-scope.mdTake every feature the founder mentioned (or infer them from the idea) and sort them:
| Feature | Category | Reasoning |
|---|---|---|
| ... | Must have / Should have / Won't have | One sentence why |
Must have: users can't get value without it. Remove it and the product is pointless. Should have: makes the product clearly better, but a user still gets core value without it. Build in weeks 2-4. Won't have: a fine idea, but building it before product-market fit is waste. Cut it now.
Be aggressive. Founders usually put 10 features in must have when 3-4 belong there.
State the MVP in one sentence: "A user can [do X] and [get Y outcome] in under [Z minutes]."
Then list the features that make this possible: 3-6, no more.
The critical path, from signup to value:
Step 1: User arrives at [landing page / app]
Step 2: User [action]
Step 3: User sees [result / value]
Step 4: User [conversion action: share, save, upgrade]
Each step should take under 60 seconds. If the flow needs more than 5 steps, it's too complex for an MVP.
For the MVP features only:
The top 5 features that seem important but should wait. For each:
Define "done":
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Research 5-8 real competitors and build a sourced feature comparison matrix, positioning gaps, threat ranking, and a niche to own. Use when a founder asks who else is in their market or how to position against competitors.
The English summary is being prepared. Showing the original description.
Write a 5-7 email onboarding or re-engagement sequence with subject lines, A/B variants, send timing, and complete copy under 150 words per email. Use when a founder needs lifecycle emails for a product.
The English summary is being prepared. Showing the original description.
Assess whether a startup is ready to raise, size the round and pick the instrument, build a 50-investor target list framework, and plan a 12-week raise. Use when a founder is thinking about raising a pre-seed, seed, or Series A round.
The English summary is being prepared. Showing the original description.
Plan a product launch from pre-launch audience building to a 90-day growth plan, with named communities, platform-specific launch tactics, channel rankings, and a budget for $0-$500 a month. Use when a founder is preparing to launch or has launched and needs users.
The English summary is being prepared. Showing the original description.
Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata. Use when a founder needs copy for a new or existing landing page.
The English summary is being prepared. Showing the original description.
Pick the 5 metrics that matter at a startup's current stage, with definitions, targets, actions when below target, a minimal tracking setup, and a weekly review template. Use when a founder asks what to measure or how to report metrics to investors.
The English summary is being prepared. Showing the original description.