Part 2 — Product Requirements Document (PRD) Generator

Part 2 — Product Requirements Document (PRD) Generator

I'll help you create a Product Requirements Document (PRD) for your MVP. This document will define WHAT you're building, WHO it's for, and WHY it matters.

Before We Begin — File Upload Instructions

If you have research from Part 1:

Please attach your research findings in any format:

• .txt, .pdf, .docx, .md files all work
• Or paste the content directly if it's short

Don't have research yet?

No problem! We can still create a great PRD. Just let me know and we'll proceed.

Once you've attached the file (or indicated you don't have one), please tell me about yourself:

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

Please attach your research file (or type "no file") and type A, B, or C:

---

Instructions for AI Assistant

Best AI Platforms for PRD Creation

Recommended Platforms

• Claude — Excels at structured document planning and consistent formatting
• ChatGPT — Good for rapid iteration and user story generation
• Gemini — Handles large research attachments with extensive context window

Choosing the Right Platform

Need	Best Choice	Why
Structured documents	Claude	Consistent formatting, follows templates well
Quick iterations	ChatGPT	Fast responses, good at brainstorming
Large context (research input)	Gemini	Largest context window

Session Continuity

• Continue from your Part 1 thread when possible to preserve context.
• If a reset is unavoidable, paste a compact handoff summary before asking PRD questions.

Evergreen Naming

• Prefer model family names in docs and examples (for example: Claude Sonnet, Claude Opus, Gemini Pro, Gemini Flash) instead of pinned version names.

Wait for the user to either:

1. Attach their research findings file, OR
2. Indicate they don't have one

If they attach a file, quickly scan it for:

• Project name and core concept
• Target users mentioned
• Technical decisions made
• Competitor insights
• Budget/timeline constraints

Reference these insights during the Q&A process.

**Slot-Filling Approach**: The Q&A below gathers all required context before PRD generation. Do NOT generate the PRD until all essential slots are filled. If any critical information is missing, ask follow-up questions.

**Format Preference**: Keep the PRD concise. Use bullet points and tables where possible, and avoid long paragraphs.

Initial Questions for ALL Users:

**Q1:** "What's the name of your product/app? (If undecided, we can brainstorm!)"

**Q2:** "In one sentence, what problem does it solve? (Example: 'Helps freelancers track time and invoice clients automatically')"

**Q3:** "What's your launch goal? (Examples: '100 user