oh-pdd-prd-analysis

Original：🇨🇳 Chinese

Translated

1 scriptsChecked / no sensitive code detected

Analyze HM Desktop PRD documents, extract requirement information, verify completeness, check chapter order (Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description), inspect KEP definitions, detect requirement conflicts, and generate structured analysis reports. Applicable to user requests: (1) Analyze or review PRD documents, (2) Extract KEP lists from requirements, (3) Check PRD completeness or consistency, (4) Map requirements to module architecture, (5) Verify PRD format compliance, (6) Verify completeness of competitor analysis chapters. Keywords: PRD analysis, requirement extraction, KEP verification, completeness check, chapter order validation, competitor analysis check, analyze PRD, requirement extraction, completeness check, chapter order validation

3installs

Sourceopenharmonyinsight/openharmony-skills

Added on2026-02-10

NPX Install

npx skill4agent add openharmonyinsight/openharmony-skills oh-pdd-prd-analysis

SKILL.md Content (Chinese)

View Translation Comparison →

PRD Requirement Analysis

Analyze HM Desktop PRD documents and generate structured requirement analysis reports.

Quick Start

Provide the PRD file path:

Analyze PRD: {PRD File Path}

Or specify specific options:

Analyze PRD: {PRD File Path}
- Output Format: JSON
- Check Completeness: Yes
- Extract KEP: Yes
- Detect Conflicts: Yes

Analysis Process

1. Document Metadata Parsing

Extract the following information:

Document Version (in VX.X format)
Creation Date (YYYY-MM-DD)
Document Author/Team
Product Name
Target Version

2. KEP (Key Experience Path) Extraction

For each identified KEP, extract:

KEP ID: Should be in formats like KEP1-01, KEP1-02, etc.
KEP Name: Concise, verb-included name
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 (Mandatory for release)
Number of P1 requirements (Important but non-blocking)
Number of P2 requirements (Future enhancements)

4. Completeness Verification

Verify all mandatory chapters using the checklist in references/completeness_rules.md.

Standard Chapter Order: Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description

Chapter Order Validation:

Chapter 1: Requirement Source
Chapter 2: Requirement Background
Chapter 3: Requirement Value Analysis
Chapter 4: Competitor Analysis (Mandatory)
Chapter 5: Requirement Description
Whether subsequent chapters comply with specifications

Competitor Analysis Chapter Check:

Whether there is an independent Competitor Analysis chapter (Chapter 4)
Whether the number of competitors is ≥2
Whether it includes a competitor function comparison table
Whether it includes competitor technical solution analysis

5. Chapter Order Validation

Verify if PRD document chapters comply with the standard order:

Standard Order: Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description

Detection Logic:

Extract all level-1 headings (starting with #) from the document
Verify if the first 5 chapters meet the requirements
If the order is incorrect, list the issues and suggest adjustments
If the Competitor Analysis chapter is missing, clearly prompt to supplement it

Output Format:

Chapter Order Check Results:
✅ Chapter 1: Requirement Source
✅ Chapter 2: Requirement Background
✅ Chapter 3: Requirement Value Analysis
❌ Chapter 4: Competitor Analysis (Missing, needs supplement)
✅ Chapter 5: Requirement Description

6. Conflict Detection

Check for:

Inconsistent descriptions of the same function in different chapters
Priority conflicts (Excessive P0 items)
Technical feasibility risks
Contradictory user scenarios

7. Competitor Analysis Chapter Check

Check Items:

Check Item	Description
Chapter Position	Competitor Analysis must be in Chapter 4
Number of Competitors	Analyze at least 2 competitors
Comparison Dimensions	Function, technology, experience, cost, etc.
Differentiation	Whether differential advantages are clearly stated
Evidence Support	Whether there is data or case support

Output: If Competitor Analysis is missing or insufficient, generate a supplementary suggestion template

8. Module Division Suggestions

Map requirements to service modules according to the guidelines in references/module_mapping.md.

Output Formats

Markdown Report (Default)

Generate

prd_analysis_report.md

, including:

Document Information
Requirement Overview
KEP List
Completeness Check Results
Conflict Detection Results
Module Division Suggestions

JSON Format

json

{
  "prd_info": {
    "file": "{PRD File Name}",
    "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 Verification: references/kep_validation.md
Module Mapping: references/module_mapping.md

Report Template

Customize report format, see assets/report_template.md.

Error Handling

Error Type	Handling Method
PRD File Not Found	Prompt user to check the file path
Non-Compliant Format	List missing mandatory chapters
Requirement Conflicts	List conflicts and suggested solutions
Read Failure	Check file encoding (should be UTF-8)

Usage Examples

Basic Analysis:

Analyze this PRD: {PRD File Path}

Output in JSON Format:

Analyze {PRD File Name} and output results in JSON format

Check Completeness Only:

Check if {PRD File Name} contains all mandatory PRD chapters

Extract KEP:

Extract all KEP definitions from {PRD File Name}

Detect Conflicts:

Check if there are requirement conflicts in {PRD File Name}

Module Division Suggestions:

Based on the requirements in {PRD File Name}, suggest how to divide service modules