A professional Product Requirements Document (PRD) development skill that helps product managers systematically produce high-quality product requirements documents.
Core Features
- Requirements Analysis: Extract core requirements from user descriptions and prioritize them
- PRD Document Writing: Output a structured product requirements document
- User Story Writing: Write user stories and acceptance criteria in a standard format
- Page/Functional Specifications: Define page structure, interaction flows, and state management
PRD Document Template
Standard Frontend Project PRD Structure
# [项目名称] 产品需求文档
1. Project Overview
1.1 Project Background
1.2 Project Goals
1.3 Target Users
1.4 Success Metrics
2. Functional Requirements
2.1 Feature List (arranged by priority)
| Feature Module | Priority | Description | Status |
|---|---|---|---|
| ... | P0/P1/P2 | ... | To Be Developed |
2.2 User Stories
- As a [user role], I want [feature description], so that [user value]
2.3 Page Structure
- Page list and hierarchical relationships
- Route design
3. Interaction Design Requirements
3.1 Page Flowchart
3.2 Key Interaction Description
3.3 Responsive Design Requirements
3.4 Motion Requirements
4. Data Requirements
4.1 Data Model
4.2 API Interface Definition (Mock)
4.3 State Management Design
5. Non-Functional Requirements
5.1 Performance Requirements
5.2 Browser Compatibility
5.3 Accessibility (a11y)
6. Acceptance Criteria
6.1 Functional Acceptance Checklist
6.2 Visual Acceptance Criteria
6.3 Performance Acceptance Criteria
7. Milestones and Schedule
## 工作流程
1. **接收需求**：收集用户/老板的需求描述
2. **需求分析**：拆解需求，识别核心功能和扩展功能
3. **撰写 PRD**：按照上述模板结构化输出 PRD 文档
4. **定义 Mock 数据**：为前端开发提供 Mock API 定义
5. **制定验收标准**：明确功能和视觉的验收条件
6. **输出产物**：将 PRD 保存为 `PRD.md` 文件
## 最佳实践
- **用户视角优先**：所有功能描述从用户价值出发
- **明确边界**：清晰定义"做什么"和"不做什么"
- **可量化指标**：验收标准必须可测量、可验证
- **Mock 数据先行**：定义好数据结构后再开始开发
- **渐进式细化**：先定义核心流程，再补充边缘场景
## 输出规范
- PRD 文档保存为 `PRD.md`
- Mock API 定义保存为 `mock-api.md` 或 `mock-api.json`
- 设计规范整合到 DESIGN.md（配合 getdesign-md 技能下载的设计系统）