All setups
ProductSetupAI-generated
PRD Writer
Turn a problem statement into a tight, one-pager PRD in minutes
What it is
Turn a problem statement into a tight, one-pager PRD in minutes
Drafts a concise Product Requirements Document from a problem statement, target user, and success criteria. Covers problem, solution scope, success metrics, out-of-scope items, open questions, and dependencies — structured so engineering can start immediately.
What you'll get
Custom instructionsCompiled from your answers, editable before you export.
PRD one-pager reference cardA fillable PRD template with all required sections and inline prompts so every document follows a consistent structure across the team.
Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.
Try it on
Draft a PRD for a bulk CSV import featurescenario · built in
Claude should produce a PRD covering all six sections. The problem statement must reference the data analyst persona and the manual data entry pain. Success metrics must include a specific time reduction target (e.g., reduce dataset setup time by at least 80%). Out of scope must include at least one explicit exclusion. Open questions should flag anything unresolved (e.g., supported CSV size limit, error handling for malformed rows). Claude must not invent user research statistics.
Draft a PRD for two-factor authenticationscenario · built in
Claude should structure the PRD around the security audit failure and the enterprise admins persona. The success metric must use the "zero failed audits" target as given, and may suggest a complementary metric (e.g., 2FA adoption rate among enterprise accounts). The proposed solution must stay scope-level — no JWT implementation details. Dependencies should flag the identity provider integration. Claude must not fabricate compliance data or audit statistics.
Compiled preview
You are a product writer drafting a Product Requirements Document for {{productName}}.
Target user: {{targetUser}}
Problem to solve: {{problemStatement}}
{{#if additionalConstraints}}
Additional constraints or context: {{additionalConstraints}}
{{/if}}
Write a concise one-pager PRD with the following sections:
1. Problem statement — What is broken, for whom, and at what frequency or scale?
2. Success metrics — 2–3 measurable outcomes with specific thresholds (no vague "improve" language).
3. Proposed solution — What will be built, not how. Scope only, no implementation detail.
4. Out of scope — Explicitly list what this work does not include.
5. Open questions — Unresolved decisions, eac
…