Skip to content

Part II PRD Creation

Jump to bottom
Alp Yalay edited this page Aug 10, 2025 · 1 revision

Part II: PRD Creation

Purpose

Part II transforms your app idea into a formal Product Requirements Document (PRD) that clearly defines WHAT you're building, WHO it's for, and WHY it matters. The PRD serves as the blueprint for all subsequent development phases.

Prerequisites

Required Files

  • PRD Document from Part I (strongly recommended)

Supported Formats

  • .txt, .pdf, .docx, .md files
  • Direct text paste for short content

User Classification

Same three-level system as Part I:

  • A) Vibe-coder - Limited coding experience, using AI to build
  • B) Developer - Experienced programmer
  • C) Somewhere in between - Some coding knowledge, still learning

Question Structure

Initial Questions (All Users)

  1. Product name (can be decided during process)
  2. Problem statement (one-sentence description)
  3. Launch goal (success metrics)

Path A: Vibe-coder Questions (10 Total)

  1. Target user description (job, lifestyle, tech-savviness)
  2. User journey story (narrative format)
  3. Must-have features (3-5 essentials only)
  4. Features for version 2 (intentionally delayed)
  5. Success metrics (1-2 simple measurements)
  6. Design vibe (3-5 descriptive words)
  7. Constraints (budget, timeline, platform requirements)

Path B: Developer Questions (10 Total)

  1. Target audience definition (personas, demographics)
  2. User stories (3-5 in standard format)
  3. Core MVP features with MoSCoW prioritization
  4. Success metrics (specific targets and measurements)
  5. Technical and UX requirements
  6. Risk assessment (technical, market, execution)
  7. Business model and constraints

Path C: In-Between Questions (10 Total)

  1. User identification and needs
  2. Main user flow walkthrough
  3. Must-have features with rationale (3-5 features)
  4. Features NOT in v1 (with reasoning)
  5. Success measurement approach
  6. Design and user experience preferences
  7. Constraints and requirements

Generated PRD Documents

The system produces different PRD complexity levels based on user type:

For Vibe-coders

  • Conversational language and simple explanations
  • User story format with narrative elements
  • Visual wireframes and design guidance
  • Simple metrics with clear measurement methods
  • Implementation timeline with realistic milestones
  • Definition of Done checklist for MVP completion

For Developers

  • Professional format following industry standards
  • Technical specifications and non-functional requirements
  • Architecture considerations and system design elements
  • Detailed user stories with acceptance criteria
  • Comprehensive metrics framework with OKRs
  • Risk assessment and mitigation strategies

For In-Between Users

  • Balanced approach combining simplicity with detail
  • Educational elements explaining PRD concepts
  • Practical guidance for implementation decisions
  • Clear feature prioritization with reasoning
  • Resource recommendations for learning

PRD Document Structure

All PRDs include these core sections:

Common Elements

  • Product Overview - Name, purpose, success criteria
  • Target Users - Primary personas and user needs
  • Problem Statement - What problem is being solved
  • User Journey - How users interact with the product
  • Features - Must-have, nice-to-have, and excluded features
  • Success Metrics - How success will be measured
  • Design Direction - UI/UX preferences and principles
  • Constraints - Budget, timeline, technical limitations

Additional Elements by User Level

  • Vibe-coder: Simple wireframes, step-by-step user stories
  • Developer: Technical requirements, API specifications, compliance needs
  • In-between: Learning resources, complexity analysis

Best Practices

  1. Upload research findings - Part I research significantly improves PRD quality
  2. Be specific about features - Clearly define what's included and excluded
  3. Set realistic constraints - Honest about budget and timeline limitations
  4. Focus on MVP scope - Resist feature creep during definition
  5. Define success clearly - Measurable outcomes, not vanity metrics

AI Model Recommendations

Best Models for PRD Creation (2025)

  • Claude 4.1 Opus - Best for structured documents
  • GPT-5 - Good for user story generation
  • Gemini 2.5 Pro - Best for long context if research is extensive

Time Investment

  • Question answering: 10-15 minutes
  • PRD generation: 5-10 minutes
  • Total time: 15-25 minutes

Output Files

Generated PRD saved as:

  • PRD-[AppName]-MVP.md

Validation Checklist

Before proceeding to Part III, ensure your PRD includes:

  • Core problem clearly defined
  • Target user well understood
  • 3-5 must-have features identified
  • Success metrics defined
  • Constraints acknowledged
  • Features explicitly excluded from MVP

Next Steps

After completing Part II:

  1. Save PRD as PRD-[AppName]-MVP.md
  2. Review and validate completeness
  3. Proceed to Part III: Technical Design
  4. Keep PRD as living document for future updates
Clone this wiki locally