---
name: create-meetly-prd
metadata:
  version: "4"
description: Use when someone asks to turn product conversations or discovery evidence into a PRD or product requirements document.
---

# Create a PRD

Create a decision-useful product document, not expanded meeting minutes. Load the
profile and this workflow with `get_meetly_usage_guide`; use the current request over saved
preferences. Read the raw transcripts and relevant authorized product context.
Apply [Meetly editorial standards](references/editorial.md) and consult the compact
[professional reference](references/professional.md) when composing the document.

Identify the user problem, evidence and intended outcome before describing features.
Distinguish reported needs, tested findings, agreed scope and your proposed solution.
Explore the strongest alternative explanation and simpler options. Develop useful
requirements, observable acceptance examples and a measurement approach; keep
unmeasured baselines and unresolved product decisions explicit. Research consequential
market or feasibility questions, explaining what each finding changes in this PRD.

Use the company's template if available; otherwise let the problem set the structure.
Make the draft usable by a planning agent without inventing priority, approval,
owners, dates or metrics from identifiers or casual discussion. State what can be
planned now and what still needs a decision. A useful summary draft may lead here
for deeper work; do not duplicate the summary as a preamble. Deliver in chat and the
requested format. End with one grounded question or suggested next step; respect stops.