Building & Shipping 5 guests | 13 insights

Writing Product Requirement Documents

Define clear problems and bounded solutions to maximize team velocity and creative output.

The Guide

5 key steps synthesized from 5 experts.

Crystallize the problem statement

Start by writing a concise, one sentence problem statement that focuses on a single user or business need. Ensure this statement is agnostic of any potential solutions to keep the team focused on the outcome. Reference existing user data or evidence to justify why this problem deserves prioritization now.

Featured guest perspectives

"Problem-oriented: They crystallize the problem being solved in a few strong sentences—ideally near the top of the document—to focus the brainpower of every teammate in the same direction."

— Lenny Rachitsky

Shape boundaries with the build team

Host a shaping session with design and senior engineering leads to narrow down fuzzy requests into a bounded concept. Create diagrams and breadboards that represent core concepts without specifying high fidelity visual details. Use these sessions to determine the appetite or time box for the project before deciding on features.

Featured guest perspectives

"What we need to do in a shaping session is we come out with some kind of diagram where engineers, product and design, they're saying, "We understand that." So the first thing is we are not going to start something unless we can see the end from the beginning."

— Ryan Singer

Generate a visual or narrative draft

Use AI tools to transform your initial notes or dictated context into a structured PRD draft. Focus your manual energy on refining the strategic why and the executive summary. If the project is high stakes, consider a longer narrative format to facilitate deep asynchronous feedback from leadership.

Featured guest perspectives

"A week before a product review, Snowflake product managers share a six-page document for the topic with meeting attendees that outlines the customer problem, proposed solution, risks, and other key data points around a specific product investment."

— Lenny Rachitsky

"Describe what you want in human language, get an 80% complete draft, refine it, and then ship. This is already happening with tools like ChatPRD."

— Lenny Rachitsky

Calibrate the level of detail

Adjust the implementation guidance based on the seniority and expertise of your team. Provide more detail for junior teams and less for senior builders to avoid micromanagement and encourage ownership. Use the detail dial framework to ensure you are providing enough context without over specifying technical tasks.

Featured guest perspectives

"There’s a fine line between articulating the important details of a project spec and spending three pages explaining one button. This annoying habit can apply to both the beginning of a project, telling designers and engineers exactly how a feature needs to work, and also at the end when you spec out each feature for days."

— Lenny Rachitsky

Verify and audit for clarity

Review the final document for readability and ensure it includes a non-goals section to prevent scope creep. Ask technical questions about database requirements and architectural trade-offs early to avoid late stage surprises. Study past successful 1-pagers within your company to align your spec with the local standard of greatness.

Featured guest perspectives

"A reminder of how valuable it is to keep these to one page, at least to start"

— Lenny Rachitsky

Get this guide as an AI skill for Claude Code

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

Quick Install (Recommended)

Install this skill directly using npx:

npx skills add RefoundAI/lenny-skills --skill writing-prds

Or install all 76 skills:

npx skills add RefoundAI/lenny-skills

View on GitHub →

Manual Installation

Download the skill

Download Skill (.zip)

Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/writing-prds/SKILL.md

Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with writing product requirement documents

Guest Perspectives

Deep dive into what 4 podcast guests shared about writing product requirement documents.

Jenny Wen 1 quote

"We used to go off and make this two-year, five-year, 10-year vision even. Now it becomes a vision that's three to six months out, and isn't necessarily creating this beautiful deck, sometimes just creating a prototype that points people in the right direction."

Tactical:

Replace multi-year vision decks with three-to-six-month directional prototypes.
Reduce time spent on high-fidelity mocks to prioritize supporting engineers with 'last mile' implementation and polish.
Test functional prototypes with actual models to account for the non-deterministic nature of AI behavior.

View all skills from Jenny Wen →

Melanie Perkins 1 quote

Listen to episode →

"So we have this concept of chaos to clarity and every idea starts in the chaos side, and then you have to work all the way to the other side, which is clarity. And so chaos can be an idea, it can be a problem, it can be a philosophy or a belief."

Tactical:

Add clarity to every abstract idea by forcing yourself to write it down as the very first step.
Develop a visual vision deck for every new project to make the intended outcome visible to the team.
Iterate through designs and prototypes to refine the concept before seeking mastery or total answers.

View all skills from Melanie Perkins →

Ryan Singer 1 quote

Listen to episode →

"What we need to do in a shaping session is we come out with some kind of diagram where engineers, product and design, they're saying, "We understand that." So the first thing is we are not going to start something unless we can see the end from the beginning."

Tactical:

Gather product, design, and senior engineering leads for short, high-intensity collaborative sessions.
Create diagrams that represent the core concept without getting bogged down in high-fidelity details.
Verify technical feasibility early to avoid drastic changes in cost or time during the build.

View all skills from Ryan Singer →

Vijay 1 quote

Listen to episode →

"And if you're shipping features that quick leads, you don't have time to stop and think, where does this go, and how does this fit into our overall system architecture? And what started to happen was that we were hitting diminishing returns with some of these features. And not considering the holistic design and consistency meant the reach of every feature was low."

Tactical:

Identify the minimal number of core building blocks required for your product's system architecture.
Pivot to a design-led initiative to ensure consistency once high-velocity shipping begins to fragment the user experience.
Establish design as a key differentiator to improve feature discoverability and reach across the platform.

View all skills from Vijay →