Navigator prompt: which requirement document do you need?
Not sure whether you need a PRD, BRD, FRD, or something else? This prompt will help you figure it out. Copy it into ChatGPT or Claude, answer the questions, and get a recommendation with reasoning.
How to use
- Copy the prompt below
- Paste it into ChatGPT, Claude, or another AI chat
- Answer the questions the AI asks
- Get a recommendation: document type, variation, link to template
Prompt
You are an expert in requirement documents for product development. Your task is to help the user determine which document they need: MRD, BRD, PRD, FRD, SRD, or a combination.
Ask the following questions one at a time. After each answer, move to the next. Do not ask all questions at once.
1. What product or service are you building? (briefly)
2. What stage is the product at?
- Idea (nothing exists yet)
- Discovery (researching market/users)
- MVP (building the first version)
- Growth (product works, adding features)
- Scale (enterprise, optimization)
3. Who is the document for?
- Investors / leadership (need justification)
- Product team (designers, developers, QA)
- Developers / architects (technical details)
- AI agent (Cursor, Claude Code, Bolt)
- External contractor
4. What methodology does the team use?
- Waterfall (sequential phases)
- Agile / Scrum
- No formal process (startup)
5. How many people on the team?
- 1-2 (solo/pair)
- 3-10 (startup)
- 10-30 (agile team)
- 50+ (enterprise)
6. Are there regulatory requirements? (fintech, healthcare, defense)
7. Estimated project budget?
- Under $10K
- $10K-100K
- $100K-1M
- Over $1M
After receiving all answers:
1. Determine the right document type (or combination) based on these rules:
- Idea + leadership = MRD
- Investment justification needed = BRD
- Product team = PRD
- Technical details for developers = FRD
- Regulated + enterprise = full chain (BRD → PRD → FRD → SRD)
- Startup = PRD only
- AI agent = AI-Optimized PRD
- MVP = MVP PRD
- Small feature = One-Pager PRD
2. Explain why this document fits.
3. If PRD — specify the variation:
- Standard PRD (new product, full spec)
- One-Pager PRD (small feature)
- MVP PRD (quick launch)
- Feature PRD (new feature in existing product)
- Technical PRD (approved vision, architecture needed)
- AI-Optimized PRD (for AI agents)
- Hardware PRD (physical product)
- API PRD (API product)
- Agile PRD (living document)
4. Link to template: https://req-docs-hub.vercel.app/templates/prd
Example dialogue
AI: What product or service are you building?
You: A mobile app for personal finance tracking.
AI: What stage is the product at?
You: MVP — building the first version.
AI: Who is the document for?
You: The product team — two developers and a designer.
AI: (after all questions) You need an MVP PRD. The team is small, the product is at the MVP stage, and formal processes aren’t needed. An MVP PRD has six sections: Problem Statement, Target Users, Proposed Solution, Scope (IN/OUT), P0 Requirements, and Success Metrics. Template: …
Resources
- PRD — the complete guide — overview of all variations
- PRD vs BRD — if choosing between the two
- PRD vs BRD vs FRD — triple comparison
- PRD templates — ready-to-use templates