create-prd

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Generating a Product Requirements Document (PRD)

生成产品需求文档（PRD）

Goal

目标

To guide an AI assistant in creating a detailed Product Requirements Document (PRD) in Markdown format, based on an initial user prompt. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement the feature.

指导AI助手基于用户初始提示，生成Markdown格式的详细产品需求文档（PRD）。输出的PRD应当清晰、可落地，能够让初级开发人员理解并实现对应功能。

Process

流程

Receive Initial Prompt: The user provides a brief description or request for a new feature or functionality.
Ask Clarifying Questions: Before writing the PRD, the AI must ask only the most essential clarifying questions needed to write a clear PRD. Limit questions to 3-5 critical gaps in understanding. The goal is to understand the "what" and "why" of the feature, not necessarily the "how" (which the developer will figure out). Make sure to provide options in letter/number lists so I can respond easily with my selections.
Generate PRD: Based on the initial prompt and the user's answers to the clarifying questions, generate a PRD using the structure outlined below.
Save PRD: Save the generated document as
```
prd-[feature-name].md
```
inside the
```
/tasks
```
directory.
Writing Standards: Follow the
```
/writing-guide
```
skill rules for voice, tone, banned words, and LLM pattern avoidance.

接收初始提示： 用户提供新功能或新能力的简要描述或需求。
询问澄清问题： 编写PRD前，AI 必须仅询问编写清晰PRD所需的最核心澄清问题，问题数量控制在3-5个，覆盖认知上的关键缺口。目标是明确功能的“是什么”和“为什么”，无需纠结“如何实现”（这部分由开发人员自行判断）。请以字母/数字列表的形式提供选项，方便我通过选择快速回复。
生成PRD： 基于初始提示和用户对澄清问题的答复，使用下文给出的结构生成PRD。
保存PRD： 将生成的文档以
```
prd-[feature-name].md
```
的文件名保存到
```
/tasks
```
目录下。
写作标准： 遵循
```
/writing-guide
```
技能规则，符合语气、禁用词、规避大语言模型模式的相关要求。

Clarifying Questions (Guidelines)

澄清问题（指导原则）

Ask only the most critical questions needed to write a clear PRD. Focus on areas where the initial prompt is ambiguous or missing essential context. Common areas that may need clarification:

Problem/Goal: If unclear - "What problem does this feature solve for the user?"
Core Functionality: If vague - "What are the key actions a user should be able to perform?"
Scope/Boundaries: If broad - "Are there any specific things this feature should not do?"
Success Criteria: If unstated - "How will we know when this feature is successfully implemented?"

Important: Only ask questions when the answer isn't reasonably inferable from the initial prompt. Prioritize questions that would significantly impact the PRD's clarity.

仅询问编写清晰PRD所需的最关键问题，聚焦初始提示中存在歧义或缺少必要上下文的部分。常见需要澄清的领域包括：

问题/目标： 若表述不清则询问：“该功能为用户解决什么问题？”
核心功能： 若表述模糊则询问：“用户应当能够执行的关键操作有哪些？”
范围/边界： 若范围过宽则询问：“该功能有哪些明确不支持的内容？”
成功标准： 若未说明则询问：“我们如何判断该功能已成功落地？”

重要提示： 仅当从初始提示中无法合理推断出答案时再提问，优先选择会显著影响PRD清晰度的问题。

Formatting Requirements

格式要求

Number all questions (1, 2, 3, etc.)
List options for each question as A, B, C, D, etc. for easy reference
Make it simple for the user to respond with selections like "1A, 2C, 3B"

所有问题添加编号（1、2、3等）
每个问题的选项以A、B、C、D等序号列出，方便查阅
让用户可以轻松通过类似“1A, 2C, 3B”的形式回复选择

Example Format

示例格式

1. What is the primary goal of this feature?
   A. Improve user onboarding experience
   B. Increase user retention
   C. Reduce support burden
   D. Generate additional revenue

2. Who is the target user for this feature?
   A. New users only
   B. Existing users only
   C. All users
   D. Admin users only

3. What is the expected timeline for this feature?
   A. Urgent (1-2 weeks)
   B. High priority (3-4 weeks)
   C. Standard (1-2 months)
   D. Future consideration (3+ months)

1. What is the primary goal of this feature?
   A. Improve user onboarding experience
   B. Increase user retention
   C. Reduce support burden
   D. Generate additional revenue

2. Who is the target user for this feature?
   A. New users only
   B. Existing users only
   C. All users
   D. Admin users only

3. What is the expected timeline for this feature?
   A. Urgent (1-2 weeks)
   B. High priority (3-4 weeks)
   C. Standard (1-2 months)
   D. Future consideration (3+ months)

PRD Structure

PRD结构

The generated PRD should include the following sections:

Introduction/Overview: Briefly describe the feature and the problem it solves. State the goal.
Goals: List the specific, measurable objectives for this feature.
User Stories: Detail the user narratives describing feature usage and benefits.
Functional Requirements: List the specific functionalities the feature must have. Use clear, concise language (e.g., "The system must allow users to upload a profile picture."). Number these requirements.
Non-Goals (Out of Scope): Clearly state what this feature will not include to manage scope.
Design Considerations (Optional): Link to mockups, describe UI/UX requirements, or mention relevant components/styles if applicable.
Technical Considerations (Optional): Mention any known technical constraints, dependencies, or suggestions (e.g., "Should integrate with the existing Auth module").
Success Metrics: How will the success of this feature be measured? (e.g., "Increase user engagement by 10%", "Reduce support tickets related to X").
Open Questions: List any remaining questions or areas needing further clarification.

生成的PRD应当包含以下章节：

介绍/概述： 简要描述功能及其解决的问题，说明目标。
目标： 列出该功能具体、可衡量的预期成果。
用户故事： 详细说明描述功能使用方式和价值的用户叙事。
功能需求： 列出该功能必须具备的具体能力，使用清晰简洁的表述（例如：“系统必须允许用户上传头像”），为这些需求添加编号。
非目标（超出范围）： 明确说明该功能不会包含的内容，以管控范围。
设计考量（可选）： 关联设计稿、描述UI/UX需求，或提及相关的组件/样式（若适用）。
技术考量（可选）： 提及已知的技术约束、依赖项或建议（例如：“应当与现有Auth模块集成”）。
成功指标： 如何衡量该功能的成功？（例如：“用户参与度提升10%”、“与X相关的支持工单减少”）。
待澄清问题： 列出所有遗留问题或需要进一步明确的领域。

Target Audience

目标受众

Assume the primary reader of the PRD is a junior developer. Therefore, requirements should be explicit, unambiguous, and avoid jargon where possible. Provide enough detail for them to understand the feature's purpose and core logic.

假设PRD的主要读者是初级开发人员，因此需求应当明确、无歧义，尽可能避免使用行话。提供足够的细节，让他们能够理解功能的用途和核心逻辑。

Output

输出

Format: Markdown (
```
.md
```
)
Location:
```
/prd/
```
Filename:
```
prd-[feature-name].md
```

格式： Markdown（
```
.md
```
）
存储位置：
```
/prd/
```
文件名：
```
prd-[feature-name].md
```

Final instructions

最终说明

Do NOT start implementing the PRD
Make sure to ask the user clarifying questions
Take the user's answers to the clarifying questions and improve the PRD

不要直接开始实现PRD对应功能
务必向用户询问澄清问题
结合用户对澄清问题的答复优化PRD内容