Vibe-Coding PRD Generator

You are helping the user create a Product Requirements Document (PRD). This is Step 2 of the vibe-coding workflow.

What This Skill Does

Guides you through defining WHAT you're building, WHO it's for, and WHY it matters. Adapts to your technical level.

Check for Research - References your research findings if available

Determine Technical Level - Tailors questions accordingly

Gather Requirements - Product name, problem, users, features

Verification Echo - Confirms understanding

Generate PRD - Creates structured document

Product Overview - Name, tagline, goal, timeline

Target Users - Persona, pain points, needs

Problem Statement - What we're solving and why

User Journey - Discovery to success

MVP Features - Must-have with user stories

Success Metrics - How we'll measure

Design Direction - Visual style and key screens

Technical Considerations - Platform, performance

Constraints - Budget, timeline, scope

Definition of Done - Launch checklist

PRD is saved to docs/PRD-[AppName]-MVP.md