Product Requirements Document (PRD)
The Product Requirements (PRD) defines the product's core goals, value, target users, and success criteria. It organizes the requirements that serve as the starting point of planning, and lays the foundation for the Functional Specification and User Flow that follow.
PRD Components
On the Product Requirements page, you can fill in the following content.

Overview: A one-line definition of the product, the product goals you want to achieve, and background from a business or market perspective.
Problem & Solution: The problem users face, how the product solves it, and how it differentiates from competitors.
Target & Scenario: Definitions of key user groups, and usage scenarios that describe the actual user journey as a story.
Success & Risks: The core KPIs used to judge product success, along with anticipated risks and open issues.
Project Basics: The product category, the user roles defined for this Project (e.g. admin, customer), and the environments the service will run in (e.g. Web, iOS).
"User roles" are later connected directly to Features in the Functional Specification.
Reviewing and Editing the PRD
Based on the PRD draft generated by AI, you can freely edit and refine the content to complete your plan.

1. Intuitive Inline Editing
You can edit the text directly without entering a separate edit mode — just click the text you want to change.
All changes are saved in real time, so you don't need to press a save button.
When you drag to select text, a toolbar appears letting you apply various styles such as bold (B), italic (I), strikethrough, and lists to improve readability.
2. Partial Edits with AI
You can select a specific sentence or paragraph and ask the AI to refine it precisely.
Drag to select the sentence you want to revise, then click the [AI icon (✨)] that appears.
In the 'How should I revise it?' input, enter a specific direction like "Use more professional terminology" or "Emphasize differentiation from competitors."
Apply the result: Review the AI's suggested revision and click [Approve] if you like it, or [Reject] if it needs further refinement — improving the quality of your plan with each iteration.
3. Whole-Document Optimization
Use the [Ask AI to revise] button in the top right to align the tone of the whole document or address logical gaps.
When the AI proposes a revision, you can preview the result. If the content looks good, click [Approve]; if it needs more work, click [Reject].
Last updated

