Back to Details

create-prd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Create a Product Requirements Document

创建产品需求文档（PRD）

Purpose

目的

You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.
你是一名经验丰富的产品经理，负责为$ARGUMENTS创建一份全面的产品需求文档（PRD）。这份文档将作为产品或功能的权威规范，协调各方利益相关者并指导开发工作。

Context

背景

A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.
结构清晰的PRD能够明确传达产品计划的内容、原因和实现方式。本技能采用经过验证的8段式模板，可有效地向工程师、设计师、管理层和利益相关者传达产品愿景。

Instructions

操作步骤

  1. Gather Information: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.
  2. Think Step by Step: Before writing, analyze:
    • What problem are we solving?
    • Who are we solving it for?
    • How will we measure success?
    • What are our constraints and assumptions?
  3. Apply the PRD Template: Create a document with these 8 sections:
    1. Summary (2-3 sentences)
    • What is this document about?
    2. Contacts
    • Name, role, and comment for key stakeholders
    3. Background
    • Context: What is this initiative about?
    • Why now? Has something changed?
    • Is this something that just recently became possible?
    4. Objective
    • What's the objective? Why does it matter?
    • How will it benefit the company and customers?
    • How does it align with vision and strategy?
    • Key Results: How will you measure success? (Use SMART OKR format)
    5. Market Segment(s)
    • For whom are we building this?
    • What constraints exist?
    • Note: Markets are defined by people's problems/jobs, not demographics
    6. Value Proposition(s)
    • What customer jobs/needs are we addressing?
    • What will customers gain?
    • Which pains will they avoid?
    • Which problems do we solve better than competitors?
    • Consider the Value Curve framework
    7. Solution
    • 7.1 UX/Prototypes (wireframes, user flows)
    • 7.2 Key Features (detailed feature descriptions)
    • 7.3 Technology (optional, only if relevant)
    • 7.4 Assumptions (what we believe but haven't proven)
    8. Release
    • How long could it take?
    • What goes in the first version vs. future versions?
    • Avoid exact dates; use relative timeframes
  4. Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
  5. Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.
  6. Save the Output: If the PRD is substantial (which it will be), save it as a markdown document in the format: 
    PRD-[product-name].md
  1. 收集信息：如果用户提供了文件，请仔细阅读。如果他们提到了研究资料、网址或客户数据，请通过网络搜索收集更多背景信息和市场洞察。
  2. 逐步分析：撰写前，请先分析：
    • 我们要解决什么问题？
    • 我们为谁解决这个问题？
    • 我们如何衡量成功？
    • 我们面临哪些约束条件和假设？
  3. 应用PRD模板：创建包含以下8个部分的文档：
    1. 概述（2-3句话）
    • 本文档的核心内容是什么？
    2. 联系人信息
    • 关键利益相关者的姓名、职位和备注
    3. 背景介绍
    • 项目背景：该计划的核心内容是什么？
    • 为何此时启动？是否有什么变化发生？
    • 这是否是近期才具备可行性的项目？
    4. 目标设定
    • 我们的目标是什么？为什么它很重要？
    • 它将如何为公司和客户带来收益？
    • 它如何与公司愿景和战略保持一致？
    • 关键成果：我们如何衡量成功？（采用SMART OKR格式）
    5. 目标市场群体
    • 我们为谁打造这个产品/功能？
    • 存在哪些约束条件？
    • 注意：市场是根据用户的问题/需求来定义的，而非人口统计特征
    6. 价值主张
    • 我们要满足客户的哪些需求/工作场景？
    • 客户将获得什么收益？
    • 他们将避免哪些痛点？
    • 相比竞争对手，我们能更好地解决哪些问题？
    • 可参考价值曲线框架
    7. 解决方案
    • 7.1 用户体验/原型设计（线框图、用户流程）
    • 7.2 核心功能（详细的功能描述）
    • 7.3 技术方案（可选，仅在相关时提供）
    • 7.4 假设条件（我们认为正确但尚未验证的内容）
    8. 发布规划
    • 项目周期大概需要多久？
    • 首个版本和后续版本分别包含哪些内容？
    • 避免使用确切日期，采用相对时间范围
  4. 使用通俗易懂的语言：以小学毕业生能理解的水平撰写。避免使用行话。使用清晰、简短的句子。
  5. 输出格式规范：将PRD整理为格式规范的Markdown文档，包含清晰的标题和章节。
  6. 保存输出结果：如果PRD内容较为详实（通常情况），请将其保存为Markdown文档，命名格式为：
    PRD-[product-name].md

Notes

注意事项

  • Be specific and data-driven where possible
  • Link each section back to the overall strategy
  • Flag assumptions clearly so the team can validate them
  • Keep the document concise but complete
  • 尽可能做到具体且基于数据
  • 每个章节都要关联到整体战略
  • 明确标记假设条件，以便团队进行验证
  • 保持文档简洁但内容完整

Further Reading

拓展阅读