Generated with Ancher · published 2026-08-24
Product requirements document
The PRD prompt to run before you write a single line of code
Define the problem, user journey, MVP scope, priorities, effort, success metric, constraints, and phase-two risks before development starts.
The prompt
MVP product requirements document
A directly usable prompt preserved from the original X post.
Create a Product Requirements Document for [project name]. Include: - Problem statement: the exact user pain this solves in one sentence - Target user: one specific persona (not 'everyone') - Core user journey: what the user does from signup to first value, step by step - MVP feature list: only features required for that core journey. Nothing else. - Out of scope: explicitly list what we are NOT building in v1 - Success metric: one number that tells us if this worked in 30 days - Tech constraints: stack, integrations, third-party APIs required - Open questions: things we need to decide before dev starts For each feature in the MVP list, add: priority (P0/P1/P2), estimated complexity (S/M/L), and which user journey step it serves. Flag anything that sounds like a phase 2 feature disguised as a phase 1 requirement.
Source trail
Original X post
The author, media, context, and direct source remain attached.

Vibe coding PRO TIP : The exact PRD prompt i paste into Cursor before writing a single line of code. Drop this in at the start of every new project: --- "Create a Product Requirements Document for [project name]. In…
See the original post →What you’ll get
- Problem and evidence
- Goals
- User needs
- Requirements
- Scope and tradeoffs
- Success criteria
What to provide
Bring the source material. Ancher shapes the deliverable.
Customer research, product notes, existing requirements, constraints, and team decisions.