vibe-prd

# 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 1. Reuse prior research context instead of restarting in an empty chat. 2. Ask for a compact handoff summary if the user restarted sessions. 3. 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: 1. Look for `docs/research-*.md` (or `*.txt` for backward compatibility) in the project 2. If found, read it and reference insights during Q&A 3. 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. 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 ...