Draft PRDs from internal context
Write product requirements documents using Linear, Slack, meeting notes, and source documents.
Pair ZeroTwo's $documents skill with plugins like Linear, Slack, Notion, or Google Drive, and it writes a PRD ready for review, complete with the usual sections, timeline, decisions, open questions, and a sources appendix.
Related links
Skills & Plugins
- DocumentsWrites the PRD as a
.docxfile ($documents). - SlackReads product discussions and launch threads.
- LinearReads projects, issues, and acceptance criteria.
- Google DriveReads planning docs, research notes, and specs.
- NotionReads roadmap pages, project notes, and team wikis.
Starter prompt
Introduction
The context for a PRD usually already sits in tickets, chat and docs; ZeroTwo can gather it through your connectors and keep the trail visible.
Choose the sources
Name the Linear project, Slack thread and Drive or Notion docs, and spell out the sections you want. Review the appendix first, then requirements and open questions.
Refine in the same chat
Point the agent at missing sources rather than restarting.
Check the source trail
Before sharing, have it list weakly supported claims, unowned questions and decisions treated as settled.
Suggested prompt
Check this PRD's source trail: unsupported requirements, open questions, assumed decisions.
Related use cases
Coordinate new-hire onboarding
Assemble onboarding trackers, team summaries, and drafts for a welcome space.
Prepare meeting briefs
Convert what is on your calendar into an agenda and a notes outline.
Run event playbooks
Set up repeatable workflows for managing event programs.


