$npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-prdCreate a buildable MVP PRD. Use after the Idea Brief and Evidence Pack exist when the user needs pages, user journey, P0/P1 features, acceptance criteria, data objects, success metrics, design direction, risks, and Definition of Done.
| 1 | # MVP PRD |
| 2 | |
| 3 | Create `docs/BuildablePRD-[AppName].md`. |
| 4 | |
| 5 | ## Inputs |
| 6 | |
| 7 | Read: |
| 8 | |
| 9 | - `docs/IdeaBrief-*.md` |
| 10 | - `docs/EvidencePack-*.md` |
| 11 | |
| 12 | Ask one question at a time for missing product name, target user, core journey, must-have features, exclusions, success metrics, key screens, data objects, design direction, and privacy constraints. |
| 13 | |
| 14 | ## Output |
| 15 | |
| 16 | The PRD must include: |
| 17 | |
| 18 | - Product overview |
| 19 | - Problem and promise |
| 20 | - User journey |
| 21 | - Information architecture |
| 22 | - P0/P1/not-in-MVP features |
| 23 | - Acceptance criteria for every P0 feature |
| 24 | - Data model draft |
| 25 | - Success metrics |
| 26 | - Design direction |
| 27 | - Risks and assumptions |
| 28 | - Definition of Done |
| 29 | |
| 30 | ## Rules |
| 31 | |
| 32 | - No vague feature names without actions and data. |
| 33 | - Every P0 feature must be testable. |
| 34 | - Move complex or uncertain ideas to "Not in MVP". |