Skip to main content
Vibe-Coding Workflow
STEP 2/vibe-prd

Vibe PRD

Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".

npx skills add https://github.com/khazp/vibe-coding-prompt-template --skill vibe-prd

What is a PRD in vibe coding?

A PRD in vibe coding is the product requirements document for the first release. This skill writes it after Vibe Research when a research note exists. It records the product overview, users, problem, journey, must-have features, success metrics, design direction, constraints, and a definition of done.

It does not choose the stack. That decision belongs in the technical design. A copyable PRD template for vibe coding, and a public worked example, are in the PRD guide. The full question flow is Part II of the prompt template.

How to use the Vibe PRD skill

  1. Run /vibe-prd after Vibe Research, or open the PRD stage in the app.
  2. Answer the questions for your level.
  3. Save the result. The skill writes docs/PRD-[AppName]-MVP.md.
  4. Check that every must-have feature has an observable acceptance check and that the non-goals are explicit.

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.


The PRD Process


  • 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

    • PRD Structure


  • 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

    • Output Location


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

    Previous
    Vibe Research
    Next
    Vibe Tech Design

    Other Skills in the Workflow

    Vibe Workflow
    /vibe-workflow
    Vibe Research
    /vibe-research
    Vibe Tech Design
    /vibe-techdesign
    Vibe Agents
    /vibe-agents
    Vibe Build
    /vibe-build

    Want all 6 skills?

    Download the complete Vibe Coding skill set and transform your Claude Code workflow.

    Explore More

    All Skills →Workflow Pipeline →Prompt Templates →Coding Workflow Guide →Deep Research →PRD Generator →Technical Design →For Vibe Coders →For Developers →

    Analytics Preferences

    Optional analytics help us improve the tool. API keys stay local in your browser. Privacy