General PRD Template

1. Value Proposition

Write this section as bullet points. Use the feature context, target users, current pain points, and competitive alternatives to generate a clear value proposition.

Target User: Describe who this feature is for, including the user segment, role, scenario, constraints, and level of urgency.
User Problem / JTBD: Explain the core problem the user is trying to solve and the progress they want to make.
Current Situation: Describe how users handle this problem today, including existing workflows, tools, workarounds, and friction.
Product Value: Explain how this feature solves the problem better than the current approach or available alternatives.
Expected Outcome: Describe what becomes clearer, faster, easier, safer, or more valuable after the user adopts this feature.
Alternatives: Identify what users could use instead and why this feature should be preferred.

2. Objectives

Write this section as bullet points. Each objective should describe an intended user outcome, product outcome, or measurable success signal for the feature.

Define the primary user outcome this feature should enable.
Clarify the key user decisions, behaviors, or workflows this feature should support.
Describe what users should be able to understand, complete, compare, or improve after using this feature.
Identify the product or business goals this feature contributes to.
List measurable success indicators, such as usage, completion rate, conversion, retention, time saved, error reduction, or satisfaction.
Define the scope boundaries by stating what this feature should not solve in the MVP version.

3. Mockups (MVP Version)

Create one table row for each static page in the new feature. Place the static page screenshot or mockup on the left. On the right, first describe the changes, then list all functions currently present on the page, and finally explain the interactions and page-to-page navigation.

Static Page / Screenshot	Description
[Page Name / Static Screen Name] Insert the static screenshot, wireframe, or mockup for this page here. If no screenshot is available yet, describe the intended layout structure. Page purpose: [Briefly describe what this page is for in one sentence.]	[Page Name] 1. Changes Describe what is newly added, removed, or changed on this page compared with the existing product or previous flow. Call out changes to layout, information hierarchy, content, visual states, data shown, or user workflow. Explain why the change is needed and what user problem or product objective it supports. 2. Current Page Functions List every function, module, component, input, button, control, card, tab, filter, menu, and content area visible on this page. For each function, describe what it does, what data it displays or collects, and what state it can have. Include empty states, loading states, error states, disabled states, and permission-related states if relevant. 3. Interaction & Navigation Describe how users interact with each clickable, editable, selectable, or expandable element on this page. Specify what happens after each interaction, including modal opening, drawer expansion, content refresh, validation, toast, or state change. Describe how this page connects to other pages, including entry points, exit points, back behavior, and page-to-page navigation rules.

Static Page / Screenshot

Description

[Page Name / Static Screen Name]

Insert the static screenshot, wireframe, or mockup for this page here.
If no screenshot is available yet, describe the intended layout structure.

Page purpose: [Briefly describe what this page is for in one sentence.]

[Page Name]

1. Changes

Describe what is newly added, removed, or changed on this page compared with the existing product or previous flow.
Call out changes to layout, information hierarchy, content, visual states, data shown, or user workflow.
Explain why the change is needed and what user problem or product objective it supports.

2. Current Page Functions

List every function, module, component, input, button, control, card, tab, filter, menu, and content area visible on this page.
For each function, describe what it does, what data it displays or collects, and what state it can have.
Include empty states, loading states, error states, disabled states, and permission-related states if relevant.

3. Interaction & Navigation

Describe how users interact with each clickable, editable, selectable, or expandable element on this page.
Specify what happens after each interaction, including modal opening, drawer expansion, content refresh, validation, toast, or state change.
Describe how this page connects to other pages, including entry points, exit points, back behavior, and page-to-page navigation rules.

Repeat the table row above for every static page included in the new feature MVP.