Analyze the HM Desktop PRD document and generate a structured requirement analysis report.
Quick Start
Provide the PRD file path:
分析 PRD: {PRD文件路径}
Or specify specific options:
分析 PRD: {PRD文件路径}
- 输出格式：JSON
- 检查完整性：是
- 提取 KEP：是
- 检测冲突：是
Analysis Process
1. Document Metadata Parsing
Extract the following information:
- Document version (VX.X format)
- Creation date (YYYY-MM-DD)
- Document author/team
- Product name
- Target version
2. KEP (Key Experience Path) Extraction
For each KEP found, extract:
- KEP ID: Format should be KEP1-01, KEP1-02, etc.
- KEP name: Concise name containing a verb
- Priority: P0 (critical), P1 (important), P2 (optional)
- User story: User scenario description
- Acceptance criteria: Clear verification conditions
3. Requirement Statistics
- Total number of requirements
- Number of P0 requirements (required for release)
- Number of P1 requirements (important but non-blocking)
- Number of P2 requirements (future enhancements)
4. Completeness Verification
Use the checklist in references/completeness_rules.md to verify all required chapters.
Standard chapter order: Requirement source → Requirement background → Requirement value analysis → Competitive analysis → Requirement description
Chapter order verification：
- Chapter 1: Requirement source
- Chapter 2: Requirement background
- Chapter 3: Requirement value analysis
- Chapter 4: Competitive analysis (required）
- Chapter 5: Requirement description
- Whether subsequent chapters comply with the specification
Competitive analysis chapter check：
- Whether an independent competitive analysis chapter (Chapter 4) exists
- Whether the number of competitors is ≥ 2
- Whether a competitor feature comparison table is included
- Whether competitor technical solution analysis is included
5. Chapter Order Verification
Verify whether the PRD document chapters comply with the standard order:
标准顺序：需求来源 → 需求背景 → 需求价值分析 → 竞品分析 → 需求描述
Detection logic：
- Extract all level-1 headings in the document (starting with #)
- Verify whether the titles of the first 5 chapters meet the requirements
- If the order is incorrect, list the issues and suggest adjustments
- If the competitive analysis chapter is missing, clearly prompt to add it
Output format：
章节顺序检查结果：
✅ 第1章：需求来源
✅ 第2章：需求背景
✅ 第3章：需求价值分析
❌ 第4章：竞品分析（缺失，需补充）
✅ 第5章：需求描述
6. Conflict Detection
Check:
- Inconsistent descriptions of the same feature in different chapters
- Priority conflicts (too many P0 items)
- Technical feasibility risks
- Contradictory user scenarios
7. Competitive Analysis Chapter Check
Check content：
| Check item | Description |
|---|---|
| Chapter position | Competitive analysis must be in Chapter 4 |
| Number of competitors | Analyze at least 2 competitors |
| Comparison dimensions | Features, technology, experience, cost, etc. |
| Differentiation | Whether the differentiation advantages are clearly stated |
| Evidence support | Whether there is data or case support |
Output: If the competitive analysis is missing or insufficient, generate a supplementary suggestion template
8. Module division suggestions
According to references/module_mapping.md guidance, map the requirements to service modules.
Output format
Markdown report (default)
Generate prd_analysis_report.md, including:
- Document information
- Requirements overview
- KEP list
- Completeness check results
- Conflict detection results
- Module division suggestions
JSON format
{
"prd_info": {
"file": "{PRD文件名}",
"version": "VX.X",
"date": "2026-01-31"
},
"requirements": {
"total": 25,
"p0": 8,
"p1": 12,
"p2": 5
},
"kep_list": [...],
"completeness": {...},
"conflicts": [...],
"module_suggestions": [...]
}
Reference documents
- PRD format requirements: references/prd_format.md
- Completeness rules: references/completeness_rules.md
- KEP validation: references/kep_validation.md
- Module mapping: references/module_mapping.md
Report template
For custom report formats, see assets/report_template.md。
Error handling
| Error type | Handling method |
|---|---|
| PRD file not found | Prompt the user to check the file path |
| Format does not conform to the specification | List the missing required sections |
| Requirement conflict | List the conflicts and suggested solutions |
| Read failure | Check the file encoding (should be UTF-8) |
Usage examples
Basic analysis：
分析 {PRD文件路径} 这个 PRD
Output JSON format：
分析 {PRD文件名}，以 JSON 格式输出结果
Check completeness only：
检查 {PRD文件名} 是否包含所有必需的 PRD 章节
Extract KEP：
从 {PRD文件名} 中提取所有 KEP 定义
Detect conflicts：
检查 {PRD文件名} 中是否存在需求冲突
Module division suggestions：
根据 {PRD文件名} 的需求，建议如何划分服务模块