$npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-idea-briefCreate an Idea Brief for a Web MVP. Use when the user has a rough app idea and needs to clarify the target user, problem, current workaround, smallest useful outcome, platform choice, budget, and MVP exclusions before research or PRD work.
| 1 | # MVP Idea Brief |
| 2 | |
| 3 | Turn a rough idea into `docs/IdeaBrief-[AppName].md`. |
| 4 | |
| 5 | ## Process |
| 6 | |
| 7 | Ask one question at a time: |
| 8 | |
| 9 | 1. What is the idea in one sentence? |
| 10 | 2. Who is the first target user? |
| 11 | 3. What painful situation does this user face today? |
| 12 | 4. What do they do now without this product? |
| 13 | 5. What is the smallest useful outcome the product should deliver? |
| 14 | 6. Should the first version be Web, mobile, desktop, or undecided? |
| 15 | 7. What must be excluded from the first version? |
| 16 | 8. What is the user's technical level and budget? |
| 17 | |
| 18 | ## Verification |
| 19 | |
| 20 | Before writing, echo the product idea, target user, pain, workaround, smallest useful outcome, platform, exclusions, and constraints. Wait for confirmation. |
| 21 | |
| 22 | ## Output |
| 23 | |
| 24 | Write `docs/IdeaBrief-[AppName].md` with: |
| 25 | |
| 26 | - One-sentence product |
| 27 | - First target user |
| 28 | - Problem and current workaround |
| 29 | - Smallest useful outcome |
| 30 | - MVP boundary |
| 31 | - First platform recommendation |
| 32 | - Open questions |
| 33 | - Next step: evidence research |
| 34 | |
| 35 | ## Quality Bar |
| 36 | |
| 37 | - Make vague ideas concrete. |
| 38 | - Narrow broad audiences to a first user. |
| 39 | - Do not add features beyond the user's stated goal. |
| 40 | - Make exclusions explicit. |