create-prd

@phuryn · 收录于 1 周前 · 上游提交 1 周前★ 社区精选

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

场景写prd 需求评审功能规格

适合你，如果你需要快速撰写结构化的产品需求文档

/ 下载安装

https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/create-prd ↗

/ 通过 npx 安装 校验哈希

npx oh-my-skill add phuryn/pm-skills/create-prd

/ 通过 bash 安装

curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- phuryn/pm-skills/create-prd

/ 已经装过?验证本机副本,不用重装

npx oh-my-skill verify phuryn/pm-skills/create-prd

安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。

23265GitHub stars

~751上下文体积 · 单文件

索引托管

怎么用

商店整理自技能原文 · 版本 18468a9 · 表述以原文为准

它做什么

安装后，Claude 会变成一个产品经理，帮你写出完整的《产品需求文档》（PRD）。它会按照8个固定板块（摘要、背景、目标、市场、价值主张、解决方案、发布计划等）来组织内容，并保存为 Markdown 文件。

什么时候触发

当你要求写一份产品需求文档、记录产品需求、准备功能规格说明，或者审查已有的 PRD 时触发。

装好后可以这样说

Claude 会按8个板块生成完整 PRD。

Claude 会分析已有内容并补充建议。

技能原文 SKILL.md作者撰写 · MIT · 18468a9

Create a Product Requirements Document

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.

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.

Instructions

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.

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?

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

Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.

Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.

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

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