Write a PRD Your Engineering Team Will Actually Read

I need to write a PRD for [feature or project name].

Here's everything I know so far (it's rough): [paste your notes, Slack threads, Figma comments, email threads, voice note transcription, whatever you have]

Ask me 3 questions to sharpen the scope, then write a PRD with these sections:

- Problem statement (one paragraph, no jargon, clear enough for a new hire)
- Users affected and how
- Proposed solution (what we're building, not how we'll build it)
- Success metrics (what changes and how we'll know)
- Out of scope (explicit, so we don't argue about it later)
- Open questions (decisions we haven't made yet)

Keep the language direct. If something is unclear in my notes, flag it instead of guessing.

My CEO asked for [feature] in our all-hands. I don't have much more context than that.

Based on what I know about our product and typical business goals, help me draft a PRD that:
1. States the most likely business problem this solves
2. Identifies what we'd need to validate before committing to build
3. Lists 3 alternative ways we could solve the same problem

I need to go back to the CEO with a real answer, not just "we'll build it."

This feature is already being built, but nobody wrote a PRD. I need to write one now so we have a record of why decisions were made.

Here's what I know about what's been built: [describe current state, decisions made, what's been cut]

Write a PRD that captures: what problem this solves, what was decided and what was cut, and what success looks like. Frame it as a record of intent, not a future proposal.

I need to write a PRD for deprecating [feature or system]. Yes, a deprecation PRD.

Here's context on the feature: [what it is, how many users, why we're deprecating it]

Write a structured document that includes: the case for deprecation, who is affected and how, the migration path we're offering, the communication plan (what we tell users, when, through which channels), and the success metric (what does "successfully deprecated" look like).

I need to write a PRD for [feature or project name].

Here's everything I know so far (it's rough): [paste your notes, Slack threads, Figma comments, email threads, whatever you have]

Ask me 3 questions to sharpen the scope, then write a PRD with these sections:

- Problem statement (one paragraph, no jargon, clear enough for a new hire)
- Users affected and how
- Proposed solution (what we're building, not how we'll build it)
- Success metrics (what changes and how we'll know)
- Out of scope (explicit, so we don't argue about it later)
- Open questions (decisions we haven't made yet)

Keep the language direct. If something is unclear in my notes, flag it instead of guessing.