PRD Block
Structure product requirements documents with goals, user stories, success metrics, and constraints. Capture the what and why of product development.
The PRD (Product Requirements Document) block provides a structured format for capturing product requirements. It includes sections for problem statements, goals, user stories with acceptance criteria, success metrics, and constraints.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Title | Yes | PRD document title |
| Version | No | Document version number |
| Status | No | Draft, In Review, Approved, or Obsolete |
| Author | No | Document author |
| Date | No | Creation or last update date |
| Problem Statement | No | The problem this product or feature addresses |
| Goals | No | What the product aims to achieve |
| Non-Goals | No | Explicitly out of scope items |
| User Stories | No | As a/I want/So that format with acceptance criteria |
| Success Metrics | No | Measurable outcomes with targets |
| Constraints | No | Technical, business, or resource limitations |
| Assumptions | No | Conditions assumed to be true |
| Timeline | No | Expected delivery timeframe |
Status Values
Example: Mobile App Feature PRD
A PRD for a new offline mode feature in a mobile application.
Example: Draft PRD
An early-stage PRD still being refined.
Best Practices
| Practice | Description |
|---|---|
| Focused Problem Statements | Keep problem statements focused and measurable |
| User Perspective | Write user stories from the user's perspective, not the system's |
| Acceptance Criteria | Include acceptance criteria for every user story |
| Measurable Metrics | Define success metrics that are measurable and achievable |
| Explicit Non-Goals | Explicitly state non-goals to prevent scope creep |
| Status Updates | Update status as the document progresses through review |
| Cross-References | Link to related technical documentation and designs |