原文核对：2026-10-13 · 中文正文 · 英文提示词与演示
场景定位
结合 $documents 与 Linear、Slack、Notion、Google Drive，生成带章节、时间线、决策、问题和来源附录的可审阅 PRD。
- 难度
- 入门
- 时间跨度
- 30 分钟
适合用于
- 把计划背景转成 PRD、提案、上线说明或决策备忘录的产品团队。
- 内部讨论对齐后需要快速起草 PRD 的 PM。
相关工具
创建、编辑并验证 DOCX。
读取获准的产品讨论、上线会话、决策和待跟进问题。
Slack ↗读取项目、issue、优先级、验收条件和未完成工作。
Linear ↗读取计划、研究、规范、导出会议记录和来源文件夹。
Google Drive ↗读取路线图、项目与会议笔记、团队知识库。
Notion ↗起步提示词
英文原文 · 可复制后按实际材料修改
Use $documents to create a PRD for [feature or product area] from @linear [project or milestone], @slack [channel or thread], and @google-drive or @notion [planning docs, research notes, meeting notes, or source folder].
Include the problem, users, goals/non-goals, requirements, UX, technical considerations, metrics, launch plan, risks, open questions, decisions, timeline, and source appendix.
Cite the sources behind requirement-level claims. If sources disagree, call out the conflict instead of choosing silently. Draft only. Do not post, update Linear, or share the document until I approve it.简介
PRD 用于对齐范围和要求，所需背景常已分布在 Linear 工单、Slack 讨论、Notion 或 Drive 草稿中。ChatGPT 可汇集并起草，保留来源链供审阅迭代。
选择来源
明确 Linear 项目、Slack 频道或会话，以及应引用的 Drive、Notion、会议记录或本地文件；同时规定问题、用户、需求、UX、技术、上线计划、时间线和决策等章节。
- 需要真实 DOCX 时使用 $documents。
- 直接指定项目、里程碑、频道、会话和应引用的文档。
- 给出 PRD 章节要求。
- 先审阅来源附录，再看需求和开放问题。
- 在同一对话中补缺口、缩小范围并准备交接。
继续完善同一草稿
用起步提示词生成首稿，缺什么就补充对应来源，不必重来。
检查来源链
分享前列出证据薄弱或缺失的论断、未解决问题和当作已确认的决策；来源附录不足以审计时，继续完善再导出或发布。
提示词示例
检查来源链
官方提示词
英文原文 · 可复制后按实际材料修改
Before I share this PRD, check the source trail.
List:
- requirements with weak or missing source support
- open questions that still need an owner or decision
- decisions you treated as confirmed
- any claims that should move out of the PRD and into open questions
Keep the source appendix linked and easy to audit.展开英文原文对照
Use ChatGPT with the $documents skill and connected plugins such as Linear, Slack, Notion or Google Drive to create a reviewable PRD with the expected sections, a timeline, decisions, open questions, and a source appendix.
Introduction
Before working on a new product or feature, it’s common to draft a product requirements document (PRD) to align on the scope and requirements. Most often than not, the context needed to write that PRD is already available in the team’s internal systems: tickets on Linear, discussions on Slack, drafts in Notion or Google Drive, etc. ChatGPT can gather this context and draft a PRD that you can review and iterate on, while keeping the source trail visible.
Choose the sources
Start with the sources you want ChatGPT to use: the Linear project, the Slack planning channel or thread, and any Drive docs, Notion pages, meeting notes, or local files that should be cited in the PRD. You should also clearly outline the PRD sections you expect, such as the problem, users, requirements, UX, tech, launch plan, timeline, or decisions.
- Start with $documents when the output should be a real DOCX.
- Name the sources directly: the Linear project or milestone, the Slack channel or thread, and the docs or notes ChatGPT should cite.
- Give ChatGPT the PRD section contract.
- Review the source appendix first, then the requirements and open questions.
- Use the same chat to resolve gaps, tighten scope, and prepare the handoff.
Refine in the same chat
Use the starter prompt on this page for the first draft. If something is missing, point ChatGPT at the missing source instead of starting over.
Check the source trail
Before sharing the PRD, ask ChatGPT to list the claims with weak or missing support, the unresolved questions, and the decisions it treated as confirmed. If the source appendix does not make those easy to audit, keep refining the same chat before exporting or posting anything.
Suggested prompt
Check the Source Trail
官方提示词
英文原文 · 可复制后按实际材料修改
Before I share this PRD, check the source trail.
List:
- requirements with weak or missing source support
- open questions that still need an owner or decision
- decisions you treated as confirmed
- any claims that should move out of the PRD and into open questions
Keep the source appendix linked and easy to audit.