| name | vibe-prd |
| description | 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". |
| allowed-tools | Read, Write, Glob, Grep, AskUserQuestion |
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.
Session Continuity
- Reuse prior research context instead of restarting in an empty chat.
- Ask for a compact handoff summary if the user restarted sessions.
- Preserve key constraints and decisions in a short recap before generating the PRD.
Naming Policy
Use model family names in examples and recommendations unless the user explicitly asks for exact version names.
Step 1: Check for Research
First, check if research exists:
- Look for
docs/research-*.md (or *.txt for backward compatibility) in the project
- If found, read it and reference insights during Q&A
- If not found, proceed without it
Handoff Context block? Read it first. If the research document ends with a ## Handoff Context block, pre-fill the app name, user level, platform, budget, and timeline from it, confirm them in one line ("Got it — level B, web app, ~$50/mo, 4 weeks — right?"), and skip the A/B/C question in Step 2 unless the block is missing or unclear. No Handoff Context block? Just ask — older documents won't have it.
