大多数 PRD 失败是大纲错了，不是文字差。下面 15 个 Prompt 专门生成结构骨架——标题、顺序、漏写检查清单——覆盖功能型 PRD、MVP PRD、平台 PRD、增长 PRD、bug 批量 PRD。把它当骨头，正文再用草稿类 Prompt 去填。
适合哪些场景
每次写 PRD 都从白纸开始的 PM、scope 季度工作的 tech lead、给外包写 brief 的创始人、想统一团队 PRD 形态的 design partner。
什么时候不建议这样写 Prompt
团队已经有好用的 PRD 模板时不要导入噪音。一段话就能讲清楚的 idea 也不要套整套 PRD。
Prompt 结构公式
一份 PRD 大纲 Prompt 总带这六个要素：
- 角色：让 AI 扮演谁（资深 PM / 独立创始人 / 产品设计师 / 独立开发者 / 增长负责人）。
- 上下文：阶段（想法 / MVP / 增长 / 规模化）、团队规模、流量或 ARR、平台（web / iOS / Android）、受众、限制。
- 目标：一个具体交付物——一段 PRD、一组用户故事、一个实验设计、一篇上线公告。
- 限制：时间线（本 sprint / 本季度）、要砍的范围、不能动的东西（现有流程、计费、合规）。
- 输出格式：表格、清单、可贴 ticket 的 JSON、或带标签的段落，能直接粘到 Linear / Notion / Jira。
- 示例 / 信号：1-2 份你欣赏的参考或竞品、加 1 个想避开的反例。
这套 Prompt 适合用在哪
- 新 PM onboarding 模板
- 团队间 PRD 统一形态
- PRD 写之前的 scope 自检
- PRD review（漏什么）
- 外包 / 自由职业者的 brief 骨架
15 个可直接复制的 Prompt 模板
1. 标准功能 PRD 大纲
默认大纲。PM 没强烈意见时就用它。
You are a senior PM. Generate a standard PRD outline for a single feature. Output as a markdown table of contents with H1/H2/H3 levels. Include: Summary, Problem, Goals + non-goals, Target users, Success metrics, User stories, UX flows, Functional requirements, Non-functional requirements, Dependencies, Risks, Open questions, Rollout plan, Out of scope. For each section, add a 1-line description of what goes there.可替换变量： feature, audience, team
优化建议： 输出太泛时追加：“Tag every section with whether it is required for v1, or only needed for v2+. Cut anything not required for v1.”
2. MVP 精简大纲
Generate a slim PRD outline for an MVP that ships in 4 weeks. Maximum 8 sections. Must include: thinnest slice that delivers value, what we are explicitly NOT building, success criteria, learning goals. Output as a numbered list with 1-line section descriptions.3. 平台 / 基础设施 PRD 大纲
Generate a PRD outline for an internal platform feature (not user-facing). Sections must cover: API surface, backwards compatibility, migration path, performance SLOs, observability, security model, capacity planning, sunset plan for the old thing. Mark which sections need sign-off from which team.4. 增长实验 PRD 大纲
Generate a PRD outline tailored for a growth experiment. Sections: hypothesis, primary metric, guardrail metrics, target lift + minimum detectable effect, control vs variant, sample size estimate, duration, rollback trigger, learning even if it fails. Output with each section + 1 example sentence.5. Bug 批量 / 质量 PRD 大纲
Generate a PRD outline for a quality / bug-batch sprint. Sections: bug inventory, severity scoring, prioritization rubric, root-cause categories, prevention work, regression test plan, definition of done. Format as a checklist with sign-off owners.6. AI 功能 PRD 大纲
Generate a PRD outline for a feature that uses an LLM or AI model. Must include: model choice + fallback, prompt design, eval set, hallucination handling, latency + cost budget, safety / abuse mitigation, data privacy, human-in-the-loop, kill switch. Output with sections marked v1 / v2.7. 三种 PRD 形态对比
For this feature, generate 3 alternative PRD outlines: (a) lean 1-pager, (b) standard PRD, (c) heavy-platform PRD. For each, list sections + estimated reading time. Recommend which one to use based on this context: {team size, risk, dependencies}.
Feature: {paste}8. PRD”漏什么”审计
Below is my PRD outline. Audit it against a senior PM checklist: missing sections, sections that hide multiple decisions, sections that should be 2 documents, sections that nobody will read. Output: what to add, what to merge, what to cut.
{paste outline}9. 从一句话生成 PRD 大纲
I will give you a one-sentence feature idea. Generate the full PRD outline that idea implies. Surface 5 hidden questions the sentence dodges. Outline format: markdown headings + 1-line description + 1 open question per section.
Sentence: {paste}10. 从会议记录提取大纲
Below is a 30-minute product-discussion transcript. Extract a PRD outline from it: what was decided, what was deferred, what is still in dispute. Mark each section with [decided] / [open] / [out of scope].
{paste transcript}11. 为怀疑型读者重排序
My current outline is in the order I thought of things. Reorder it for a skeptical exec who has 5 minutes. Lead with: problem + metric + ask. Push detail to appendix. Output the new order and explain each move in 1 line.
{paste current outline}12. 大纲 + 每节字数预算
Take this PRD outline and add a target word count per section. Total should not exceed 1,800 words. Mark which sections should be a table, list, or diagram rather than prose.
{paste outline}13. 大纲 + 每节责任人
For this PRD outline, assign a draft owner role per section (PM, design, eng lead, data, legal, GTM). Mark any section that needs more than one owner and explain why.
{paste outline}14. PRD 大纲 diff（旧 vs 新）
Below are two PRD outlines for the same feature, written 2 weeks apart. Diff them: what was added, removed, renamed, restructured. Infer what the team learned in those 2 weeks. End with 3 sections still missing in both.
v1: {paste}
v2: {paste}15. 单独起草”不做范围”
Draft only the "Out of scope" and "Non-goals" sections for this PRD. Format: bulleted list with 1-line rationale per item. Include at least 5 items per section. Goal: stop scope creep before the PRD is even circulated.
Feature: {paste}容易踩的坑
- 把大纲当装饰——大纲就是 PRD 的论证结构。
- 没有”不做范围”——scope 会在整个季度里慢慢膨胀。
- 没有成功指标段——没数字的 PRD 是愿望清单。
- 把开放问题埋在最底——它们应该在前面让 reviewer 来回答。
- 4 周 MVP 和 6 个月平台用同一份大纲。
- 让 AI 编出根本用不到的章节（合规、安全）。
- 在正文写完之后再调大纲——一定先锁大纲。
优化技巧
- 至少出 2 份大纲再挑——单次出大纲容易被锁死。
- 每节标 v1 / v2 / never。大部分 v2 段最后都没填。
- 加每节字数预算，避免”无限背景”陷阱。
- 在最上面写一行”这份 PRD 在回答的问题是 Q”。
- 正文前先跑一次模板 8 审计。
- 团队 /outlines 目录保留 3-4 种胜出形态复用。
- 平台 PRD 的大纲必须含”旧物迁移 / 退役”章节，否则不完整。
FAQ
- 它和 PRD 草稿 Prompt 有什么不同？: 这里只产出结构骨架（章节 + 一行描述）。正文用 PRD 草稿 Prompt 再去填。
- 所有 PRD 用同一份大纲吗？: 不。用模板 7 给每个工作项挑形态（精简 / 标准 / 平台 / 增长）。
- 什么时候锁大纲？: 正文写之前。写完再重排比一开始就错代价大得多。
- 多长算太长？: 超过 14 个 H1，reviewer 就开始扫读。多用附录而不是更多顶层章节。
- 我直接用 Notion 模板不行吗？: 重复型可以。功能特殊或模板感觉太泛时再用这些 Prompt。