PRD Writing v1.0.0
Step-by-step workflow for writing clear, actionable Product Requirements Documents.
Workflow
- Assess project state — existing codebase or greenfield?
- Ask clarifying questions — 3-5 questions with lettered options (A/B/C)
- Draft the PRD — fill in the 12-section template
- Present for review — get user feedback on problem, stories, scope
- Revise — incorporate feedback, resolve open questions
- Save — write to
docs/prd/{feature-name}.md
Rules (25 across 7 categories)
1. Discovery (Critical)
Problem-first thinking, clarifying questions, codebase exploration, stakeholder alignment.
2. Structure (Critical)
Standardized sections, executive summary, ready-to-use PRD template, consistent output location, single source of truth.
3. Requirements (High)
User personas, user stories, functional requirements, non-functional requirements.
4. Scope (High)
Out of scope definition, non-goals, dependencies and blockers.
5. Metrics (High)
Measurable success criteria, no vague language, key performance indicators.
6. Technical (Medium)
Data model documentation, authentication model, API routes, integration points.
7. Quality (Medium)
Testable acceptance criteria, iterative review with feedback.
Usage
Write a PRD for this feature
Create product requirements for user authentication
Document requirements for the analytics dashboard
Review this PRD for completeness