use-cases/draft-prds-from-sources.md +88 −0 added
1---
2name: Draft PRDs from internal context
3tagline: Create product requirements documents from Linear, Slack, source
4 documents, and meeting notes.
5summary: Use Codex with the $documents skill and connected apps such as Linear,
6 Slack, Notion or Google Drive to create a reviewable PRD with the expected
7 sections, a timeline, decisions, open questions, and a source appendix.
8skills:
9 - token: $documents
10 description: Create, edit, and verify a DOCX when the PRD should become a
11 polished file instead of chat text.
12 - token: slack
13 url: https://github.com/openai/plugins/tree/main/plugins/slack
14 description: Read product discussions, launch threads, decision notes, and
15 follow-up questions from approved channels or thread links.
16 - token: linear
17 url: https://github.com/openai/plugins/tree/main/plugins/linear
18 description: Read projects, issues, priorities, acceptance criteria, and open
19 work that should shape the PRD.
20 - token: google-drive
21 url: https://github.com/openai/plugins/tree/main/plugins/google-drive
22 description: Read planning docs, research notes, specs, exported meeting notes,
23 and source folders.
24 - token: notion
25 url: https://github.com/openai/plugins/tree/main/plugins/notion
26 description: Read roadmap pages, project notes, meeting notes, and team wikis
27 that should shape the PRD.
28bestFor:
29 - Product teams turning planning context into a PRD, proposal, launch brief,
30 or decision memo.
31 - PMs who need to draft a PRD quickly after aligning with the team in internal
32 discussions.
33starterPrompt:
34 title: Draft the PRD
35 body: >-
36 Use $documents to create a PRD for [feature or product area] from @linear
37 [project or milestone], @slack [channel or thread], and @google-drive or
38 @notion [planning docs, research notes, meeting notes, or source folder].
39
40
41 Include the problem, users, goals/non-goals, requirements, UX, technical
42 considerations, metrics, launch plan, risks, open questions, decisions,
43 timeline, and source appendix.
44
45
46 Cite the sources behind requirement-level claims. If sources disagree, call
47 out the conflict instead of choosing silently. Draft only. Do not post,
48 update Linear, or share the document until I approve it.
49 suggestedEffort: medium
50relatedLinks:
51 - label: Codex plugins
52 url: /codex/plugins
53 - label: Agent skills
54 url: /codex/skills
55 - label: Codex app
56 url: /codex/app
57---
58
59## Introduction
60
61Before 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. Codex can gather this context and draft a PRD that you can review and iterate on, while keeping the source trail visible.
62
63## Choose the sources
64
65Start with the sources you want Codex 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.
66You should also clearly outline the PRD sections you expect, such as the problem, users, requirements, UX, tech, launch plan, timeline, or decisions.
67
68
69
701. Start with `$documents` when the output should be a real DOCX.
712. Name the sources directly: the Linear project or milestone, the Slack channel or thread, and the docs or notes Codex should cite.
723. Give Codex the PRD section contract.
734. Review the source appendix first, then the requirements and open questions.
745. Use the same thread to resolve gaps, tighten scope, and prepare the handoff.
75
76
77
78## Refine in the same thread
79
80Use the starter prompt on this page for the first draft. If something is missing, point Codex at the missing source instead of starting over.
81
82## Check the source trail
83
84Before sharing the PRD, ask Codex 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 thread before exporting or posting anything.
85
86### Suggested prompt
87
88**Check the Source Trail**