← All use cases

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.

Easy
30m

Skills & Plugins

  • Documents
    Writes the PRD as a .docx file ($documents).
  • Slack
    Reads product discussions and launch threads.
  • Linear
    Reads projects, issues, and acceptance criteria.
  • Google Drive
    Reads planning docs, research notes, and specs.
  • Notion
    Reads roadmap pages, project notes, and team wikis.

Starter prompt

Use $documents to draft a PRD for the onboarding checklist redesign. Pull from the Linear project, the planning thread in Slack, and the two docs in our product folder in Drive. Include problem, goals, requirements, timeline, decisions made, and open questions, tag each requirement with where it came from, call out places where sources disagree, and end with a source appendix. Keep it as a draft and don't post it anywhere.

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