Skip to content

PRD Skeleton Drafter

Example prompt: "When I mark a row in our Notion product ideas database as 'Drafting', pull the related customer feedback and any linked Zendesk tickets, and draft a PRD skeleton in Notion with the problem, users, success metrics, scope, and open questions for me to flesh out."

The Problem

The hardest part of writing a PRD is the first blank page, not the thinking. By the time a product manager sits down to write the spec they have already done the thinking in meetings, on Slack threads, and across half a dozen support tickets — the writing-up just feels like clerical work the day it needs to happen. So the spec slips a day, then a week, and the engineering team starts the kick-off without it.

How GloriaMundo Solves It

We build a workflow triggered when a row in the Notion "Product Ideas" database moves to the "Drafting" status. An integration step reads the row's title and short description. A second integration step searches Zendesk for tickets referencing the idea's keywords from the last 90 days; a third searches the "Customer Feedback Themes" Notion page for prior mentions. An LLM step takes the title, description, and gathered evidence and drafts a PRD skeleton — a one-paragraph problem statement, a sketch of the target users with quoted evidence, two or three candidate success metrics, an in-scope/out-of-scope sketch, and a list of open questions the PM should answer. An integration step writes the draft as a new sub-page under the idea row and links the supporting tickets and feedback excerpts in an appendix. Glass Box preview shows the gathered evidence and the draft before anything is written.

Example Workflow Steps

  1. Trigger (webhook): Fires when a row in the Notion "Product Ideas" database moves to the "Drafting" status.
  2. Step 1 (integration): Read the row's title, description, and any linked records.
  3. Step 2 (integration): Search Zendesk for tickets from the last 90 days that mention the idea's keywords.
  4. Step 3 (integration): Search the Notion "Customer Feedback Themes" page for prior mentions of the same theme.
  5. Step 4 (LLM): Draft a PRD skeleton — problem statement, target users with quoted evidence, candidate success metrics, in-scope/out-of-scope sketch, open questions.
  6. Step 5 (integration): Create a new Notion sub-page under the idea row containing the draft.
  7. Step 6 (integration): Append an evidence appendix with the linked tickets and feedback excerpts.

Integrations Used

  • Notion — where the product ideas database lives and where the PRD skeleton is written
  • Zendesk — source of supporting customer tickets

Who This Is For

Product managers who hold the context in their heads but lose the writing-up time to the rest of the week, especially at scale-ups where each PM owns 3-5 in-flight specs and the engineering teams are waiting on whichever is next.

Time & Cost Saved

A first-pass PRD that gathers evidence and lays out the skeleton typically takes a PM 90 minutes to two hours, and the gap between "I should write this up" and "I sat down to write this up" tends to be days. This workflow collapses that gap; the PM opens the page with the structure and the evidence already in place, and the time goes into the decisions the skeleton surfaces rather than the assembly.