$npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-researchCreate an Evidence Pack for a Web MVP. Use after an Idea Brief exists when the user needs competitor research, user/problem evidence, feature prioritization, monetization clues, technical feasibility, and a Go/Narrow/Pause recommendation.
| 1 | # MVP Research |
| 2 | |
| 3 | Create `docs/EvidencePack-[AppName].md`. |
| 4 | |
| 5 | ## Inputs |
| 6 | |
| 7 | Read `docs/IdeaBrief-*.md` when available. Ask for missing competitors, examples, or links. |
| 8 | |
| 9 | Use current web search when market, competitor, pricing, model, or tool information could be stale. Cite source URLs with access dates for major claims. |
| 10 | |
| 11 | ## Output |
| 12 | |
| 13 | Include: |
| 14 | |
| 15 | - Go / Narrow / Pause verdict |
| 16 | - User and problem evidence table |
| 17 | - Competitor/workaround table |
| 18 | - Feature pattern and gaps |
| 19 | - MVP feature recommendation |
| 20 | - Monetization clues |
| 21 | - Technical feasibility |
| 22 | - Source notes and uncertainties |
| 23 | |
| 24 | ## Rules |
| 25 | |
| 26 | - Prefer evidence tables over long essays. |
| 27 | - Separate facts, assumptions, and uncertain claims. |
| 28 | - If evidence is weak, recommend a narrower MVP rather than forcing a positive conclusion. |