SuperAPI AI Directory
Partner中文AI newsFavorites
Skillscheck-prd

check-prd

Writing & research

View repository

Updated 10-15 21:41

About this skill

check-prd

Conduct a strict, actionable quality review of B2B PRDs or system design documents.

Supports explicit invocation (e.g., /check-prd path/to/prd.pdf) and automatic triggering (when the user explicitly requests a review of a PRD, requirement document, product plan, or enterprise system design).

Input

  • Via $ARGUMENTS file path passed in
  • or the PRD / system design document content pasted by the user
  • or an incomplete document (review based on existing content, and clearly point out missing context)

If parameters are passed in, prioritize them as the input source:

$ARGUMENTS

Preparation before review

  1. Read the document completely before evaluating each dimension.
  2. Determine and record:
    • Business attribute: self-developed internal system or commercialized product
    • Function type: business-oriented management software / tool-oriented software / transaction-oriented platform / foundational service type
    • Document scope: 0-1 system-level planning or iteration / module-level requirements
    • Whether AI features are involved
  3. Before starting the dimension-by-dimension review, mark the dimensions that are not applicable.

Applicability rules

Dimension Applicable conditions Handling when not applicable
07-Data modeling Only business-oriented management software and transaction-oriented platforms Mark as "not applicable", and only check key data structures
10-Business analysis Only commercialized products For self-developed internal systems, only check input-output analysis
03-Competitive analysis sub-items Only commercialized products For self-developed internal systems, change to references to similar systems
06-Enterprise architecture layer 6.5-6.9 Only 0-1 new system design or system-level planning For iteration requirements, only do 6.1-6.4
R8-Multi-tenant risk item Only commercialized SaaS products Mark as "not applicable"
13-AI features Only when the document involves AI features Mark as "not applicable"

Output specification

Behavioral rules that must not be violated

  • Review dimension by dimension strictly in the order listed below.
  • As soon as each dimension is completed, immediately output the detailed analysis for that dimension.
  • Do not accumulate all dimensions and summarize them together at the end.
  • Each finding must point to a specific location in the PRD, or clearly state that relevant evidence is missing.

Output format for each dimension

## 维度[编号] - [名称] ｜ 评级：[优秀 / 合格 / 待改进 / 严重缺失]

### 具体发现

**发现 1：[问题标题]** [P0/P1/P2/P3]
- PRD定位：第X节/[功能名称]
- 问题描述：[具体说明问题，不要泛泛而谈]
- 改进示例：[给出可以立刻执行的改法]

### 隐性问题推断
结合产品类型和业务场景，列出 PRD 没写但按道理必须考虑的问题。

Minimum quality standard

  • Each dimension must contain at least 3 specific findings, or 3 clear explanations of "why there is no problem".
  • Findings must be anchored to real sections, processes, pages, or fields in the PRD.
  • Recommendations must be actionable and must not be vague or general.
  • For dimension 09 (interaction design), check each page, modal, form, and key operation described in the document one by one, and clearly point out missing interaction details.

Review order

Phase 0: Product definition

  • Before reviewing any dimension, first complete the above product definition steps.

Phase 1: Business and positioning

  1. 01 Business Analysis Quality
  2. 02 Product Type Fit
  3. 03 Product Positioning Rationality

Phase 2: Scenarios and Structure

  1. 04 Scenario Analysis and User Journey
  2. 05 Document Structure Completeness
  3. 06 Architecture Design Quality

Phase 3: Detailed Design

  1. 07 Data Modeling Quality
  2. 08 Process and Role Design
  3. 09 Interaction Design Quality

Phase 4: Value and Evolution

  1. 10 Business Analysis Depth
  2. 11 MVP Strategy and Evolution Roadmap
  3. 14 Operations Plan and Effect Tracking

Phase 5: Robustness and Forward-Looking Check

  1. 12 Exception Handling and Robustness Design
  2. 13 AI Feature Design Quality

Phase 6: Final Summary

Final Report Requirements

After all dimensions have been output one by one, generate a final summary report, including:

  1. Product Finalization Statement
  2. Summary of Findings for Each Dimension
  3. Major Risk Items
  4. Issue List Sorted by P0-P3
  5. Highlights Record
  6. Top 10 Improvement Suggestions

The final report is a navigation index to the detailed output of each dimension, not a replacement.

Work Style

  • The goal is to discover blind spots and improve the document, not to embarrass the author.
  • Maintain strict requirements for evidence and specificity.
  • Adjust judgment criteria according to product type, product stage, and document scope.
  • If the document is incomplete, explain which content cannot be verified, then continue the review based on the existing evidence.