SpyBara
Go Premium

use-cases/draft-prds-from-sources.md 2026-07-08 02:01 UTC to 2026-07-14 17:03 UTC

72 added, 126 removed.

2026
Fri 17 17:00 Thu 16 20:57 Wed 15 19:58 Tue 14 17:03 Wed 8 02:01 Mon 6 22:58

name: Draft PRDs from internal context tagline: Create product requirements documents from Linear, Slack, source documents, and meeting notes. summary: Use ChatGPT with the $documents skill and connected apps 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. skills:

  • token: $documents description: Create, edit, and verify a DOCX when the PRD should become a polished file instead of chat text.

  • token: slack url: https://github.com/openai/plugins/tree/main/plugins/slack description: Read product discussions, launch threads, decision notes, and follow-up questions from approved channels or thread links.

  • token: linear url: https://github.com/openai/plugins/tree/main/plugins/linear description: Read projects, issues, priorities, acceptance criteria, and open work that should shape the PRD.

  • token: google-drive url: https://github.com/openai/plugins/tree/main/plugins/google-drive description: Read planning docs, research notes, specs, exported meeting notes, and source folders.

  • token: notion url: https://github.com/openai/plugins/tree/main/plugins/notion description: Read roadmap pages, project notes, meeting notes, and team wikis that should shape the PRD. bestFor:

  • Product teams turning planning context into a PRD, proposal, launch brief, or decision memo.

  • PMs who need to draft a PRD quickly after aligning with the team in internal discussions. starterPrompt: title: Draft the PRD body: >- 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. suggestedEffort: medium relatedLinks:

  • label: Plugins url: /codex/plugins

  • label: Agent skills url: /codex/build-skills

  • label: ChatGPT desktop app url: /codex/app

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.

  1. Start with $documents when the output should be a real DOCX.
  2. Name the sources directly: the Linear project or milestone, the Slack channel or thread, and the docs or notes ChatGPT should cite.
  3. Give ChatGPT the PRD section contract.
  4. Review the source appendix first, then the requirements and open questions.
  5. Use the same task to resolve gaps, tighten scope, and prepare the handoff.

Refine in the same task

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 task before exporting or posting anything.

Suggested prompt

Check the Source Trail