A Product Requirements Document is a structured plan that defines WHAT you're building, WHO it's for, WHY it matters, and how success will be measured. vibe-prd guides you through these elements and generates a ready-to-share document.

Do I need research before using vibe-prd?

Not required. vibe-prd will check for research docs if present and reference insights, but you can proceed without them and still get a solid PRD.

Can I customize the PRD output format?

Yes. vibe-prd tailors the PRD to your level (A/B/C) and inputs, and you can refine sections during or after generation to suit your team.

vibe-prd

Scanned

npx machina-cli add skill KhazP/vibe-coding-prompt-template/vibe-prd --openclaw

Files (1)

SKILL.md

4.8 KB

Vibe-Coding PRD Generator

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

Your Role

Guide the user through defining WHAT they're building, WHO it's for, and WHY it matters. Ask questions one at a time.

Step 1: Check for Research

First, check if research exists:

Look for docs/research-*.txt in the project
If found, read it and reference insights during Q&A
If not found, proceed without it

Ask the user:

Do you have research findings from Part 1? If so, I'll reference them. If not, we can still create a great PRD.

Step 2: Determine Technical Level

Ask:

What's your technical background?

A) Vibe-coder — Great ideas, limited coding experience

B) Developer — Experienced programmer

C) Somewhere in between — Some coding knowledge, still learning

Step 3: Initial Questions (All Levels)

Ask these first, ONE AT A TIME:

"What's the name of your product/app? (If undecided, we can brainstorm!)"
"In one sentence, what problem does it solve?"
"What's your launch goal? (Examples: '100 users', '$1000 MRR', 'Learn to build apps')"

Step 4: Level-Specific Questions

Level A (Vibe-coder):

"Who will use your app? What do they do, what frustrates them, how tech-savvy are they?"
"Tell me the user journey story: [User] has problem X, discovers your app, does Y, now they're happy because Z"
"What are the 3-5 MUST-have features for launch? Absolute essentials only!"
"What features are you intentionally saving for version 2?"
"How will you know it's working? Pick 1-2 metrics: signups, daily users, tasks completed, or feedback score?"
"Describe the vibe in 3-5 words (e.g., 'Clean, fast, professional' or 'Fun, colorful, friendly')"
"Any constraints? Budget, timeline, performance, security, platform needs?"

Level B (Developer):

"Define your target audience: Primary persona, secondary personas, jobs to be done"
"Write 3-5 user stories: 'As a [user], I want to [action] so that [benefit]'"
"List features with MoSCoW: Must have (3-5), Should have (2-3), Could have (2-3), Won't have"
"Define success metrics: Activation, Engagement, Retention, Revenue (with targets)"
"Technical/UX requirements: Performance, accessibility, platform support, security, scalability"
"Risk assessment: Technical, market, and execution risks"
"Business model and constraints: Monetization, budget, timeline, compliance"

Level C (In-Between):

"Who are your users? Primary type, main problem, current solutions they use"
"Walk through the main user flow: Arrives because..., First sees..., Core action..., Value received..."
"What 3-5 features must be in v1? For each: name, what it does, why essential"
"What are you NOT building yet? List v2 features and why they can wait"
"How will you measure success? Short term (1 month) and medium term (3 months)"
"Design/UX: Visual style, key screens, mobile responsive?"
"Constraints: Budget, timeline, non-functional requirements, tech preferences"

Step 5: Verification Echo

After ALL questions, summarize:

Let me confirm I understand your product:

Product: [Name] - [One-line description] Target User: [Primary persona] Problem: [Core problem] Must-Have Features:

[Feature 1]

[Feature 2]

[Feature 3] Success Metric: [Primary metric and target] Timeline: [Launch target] Budget: [Constraints]

Is this accurate? Should I adjust anything before creating your PRD?

Step 6: Generate PRD

After confirmation, generate the PRD document tailored to their level.

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 and success criteria
Success Metrics - How we'll measure
Design Direction - Visual style and key screens
Technical Considerations - Platform, performance, security
Constraints - Budget, timeline, scope
Definition of Done - Launch checklist

Write the PRD to docs/PRD-[AppName]-MVP.md.

After Completion

Tell the user:

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

Self-Verification:

Core problem clearly defined?

Target user well described?

3-5 must-have features listed?

Success metrics defined?

Next Step: Run /vibe-techdesign to create your Technical Design Document.

Source

git clone https://github.com/KhazP/vibe-coding-prompt-template/blob/main/.claude/skills/vibe-prd/SKILL.mdView on GitHub

Overview

Vibe-prd helps you build a clear PRD for your MVP by guiding you through WHAT you're building, WHO it's for, and WHY it matters. It uses a step-by-step interview approach, checks for existing research, and tailors questions to your skill level to produce a ready-to-share document.

How This Skill Works

Vibe-prd first checks for existing research docs, then asks you to specify your technical level. It proceeds with initial questions, followed by level-specific questions (A, B, or C). After a final verification echo, it generates a tailored PRD ready for review.

When to Use It

You need to define product requirements and write a PRD for your MVP.
You want to transform loose ideas into a structured PRD with clear scope.
You need to align stakeholders by documenting target users, problems, and must-have features.
You prefer a guided, one-question-at-a-time interview to gather essential details.
You want a PRD with defined success metrics, constraints, and launch goals.

Quick Start

Step 1: Start vibe-prd and check for any existing research docs to reference.
Step 2: Indicate your technical level (A/B/C) and answer initial questions one at a time.
Step 3: Review the verification echo and receive your tailored PRD for review.

Best Practices

Answer questions one at a time to keep the PRD focused.
Be explicit about target users, problem statements, and the value proposition.
Use MoSCoW-style prioritization for must-have, should-have, could-have features.
Define success metrics and constraints early to guide scope and decisions.
Review the verification summary with stakeholders before generating the PRD.

Example Use Cases

A startup team writes a PRD for a new onboarding flow in a SaaS product.
A mobile app team defines 3 core features for an initial MVP release.
An internal tool project captures user roles, tasks, and data requirements.
An e-commerce feature like wishlists is scoped with success metrics and timeline.
A consumer app emphasizes simplicity and speed with clear UX goals.

Frequently Asked Questions

Add this skill to your agents