Build a copy-ready PRD prompt with problem framing, target users, scope, success metrics, constraints, acceptance criteria, and launch risks.
Use this tool when you need an AI assistant to draft a product requirements document without inventing scope. Fill in the product problem, target users, must-have features, non-goals, metrics, constraints, and open questions; then copy a prompt that asks the AI to produce a structured PRD with acceptance criteria, risks, and a human review checklist.
Use this structure before asking AI for a draft: PRD readiness = specific problem + defined users + scoped requirements + non-goals + measurable success + known constraints. If one part is weak, the generated prompt tells the AI to identify missing information instead of fabricating certainty.
| Section | What the AI should produce | Quality check |
|---|---|---|
| Problem | Explain the pain, current workaround, and why it matters now. | Can a reviewer tell what user behavior should change? |
| Requirements | Separate must-have, nice-to-have, and excluded work so scope does not drift. | Are version-one boundaries clear enough for engineering? |
| Metrics | Connect product behavior to measurable activation, retention, revenue, time saved, or quality metrics. | Would the team know whether the release worked? |
| Risks | List data, privacy, operational, dependency, and rollout risks before launch. | Are assumptions and missing decisions visible? |
Red Mode rescue on 2026-05-17: existing URL upgraded from a thin static prompt into an original browser-side prompt builder with readiness scoring, task-specific fields, FAQ, JSON-LD, and stronger internal linking. No external repository content copied.