Skip to content
Fluent
Back to Hub
PMPRD Writing with Claude

How to Write a PRD with Claude Code Without Losing Your Voice

Most PRDs written with AI sound like they were written by AI. The gap is context — Claude does not know your product's language, your team's mental models, or how you frame decisions for stakeholders. This resource shows you how to encode that context in your CLAUDE.md so every PRD Claude drafts sounds like you wrote it.

PRD Writing with Claude

PRDs That Sound Like You, Not Generic AI

Claude drafts your PRD. Your CLAUDE.md makes sure it sounds like you drafted it.

Build Your Voice in CLAUDE.md
1

Add Product Identity

Your product's core value prop, the problem it solves, and the language you use internally.

2

Define Stakeholder Profiles

Who reads your PRDs. Engineering wants tradeoffs. Exec wants outcomes. Design wants constraints.

3

Log Settled Decisions

Document what has already been decided so Claude never suggests revisiting closed questions.

4

Add Working Principles

The patterns and preferences that show up in every PRD you write.

What Most PMs Get Wrong

Prompting Without Context

Asking Claude to write a PRD without a loaded CLAUDE.md is like asking a new hire to draft on day one.

Accepting the First Draft

The first output reveals gaps in your context. Treat it as a diagnostic, not a deliverable.

Using Generic Templates

Starting from a generic PRD template trains Claude to sound generic. Start from your last best PRD instead.

PRD Prompt Sequence
Load Context

Before we start, read my CLAUDE.md and confirm you understand my product, team language, and stakeholder preferences.

First Draft

Draft a PRD for [feature]. Use my standard structure and write in the voice you see in my CLAUDE.md.

Voice Check

Read the draft out loud in your head. Flag any sentence that sounds like generic AI and rewrite it.

Stakeholder Cut

Create an exec summary version of the goals section for [stakeholder name].

What a PRD-Ready CLAUDE.md Includes

Product Identity

One paragraph on what your product does, who it's for, and how you talk about it internally.

Stakeholder Map

Short profiles for each audience who reads your PRDs, including what they care about most.

Settled Decisions

A running list of choices that are off the table so Claude never reopens them.

Voice and Tone

Three to five sentences from your best existing PRDs that capture how you write.

PRD Structure

Your standard sections, in order, so Claude uses your template by default.

Write PRDs that sound like you

Key Takeaways

  • 1Encode your product's core language and team vocabulary in CLAUDE.md before opening any PRD session.
  • 2Add a stakeholder-preference section to CLAUDE.md so Claude adjusts framing for engineering, design, and exec audiences.
  • 3Use a PRD template with placeholder fields to anchor Claude's output to your existing document structure.
  • 4Run a voice-calibration prompt at the start of each session to surface any context Claude might be missing.
  • 5Review the first draft against your last three PRDs to catch where Claude defaulted to generic phrasing.
template

PRD-Ready CLAUDE.md Template

Sign in to access this template

Create a free Fluent account to unlock templates, prompt packs, and checklists.

Create free account
pmworkflowsclaude-md