How to Write a Great PRD: A Practical Guide Inspired by Matt Pocock

I used it here: https://www.youtube.com/watch?v=GK8E5xN-Tbc&t=53s

Writing a clear, actionable Product Requirements Document (PRD) is a crucial skill for any software team. Drawing from Matt Pocock’s guide on skills.sh, here’s a step-by-step approach to crafting a PRD that leads to successful projects.

---

1. Start with the Problem

Begin by asking for a detailed description of the problem you want to solve. Don’t rush this step—understand the pain points and any initial solution ideas.

2. Explore and Verify

Dive into the codebase or project context to verify assumptions and understand the current state. This ensures your PRD is grounded in reality, not just theory.

3. Relentless Interviewing

Interview stakeholders (or yourself) about every aspect of the plan. Walk through each design decision, resolve dependencies, and make sure everyone shares the same understanding.

4. Sketch Major Modules

Outline the major modules you’ll need to build or modify. Look for opportunities to create “deep modules”—components that encapsulate lots of functionality behind a simple, stable interface. These are easier to test and maintain.

5. Align on Modules and Testing

Check with stakeholders that your module breakdown matches their expectations. Decide which modules need tests and what kind of tests are appropriate.

6. Write the PRD Using a Template

Use this template to structure your PRD:

---

Problem Statement

Describe the problem from the user’s perspective.

Solution

Describe the solution from the user’s perspective.

User Stories

A long, numbered list of user stories in the format:

• As a , I want , so that

Implementation Decisions

List the modules, interfaces, technical clarifications, architectural decisions, schema changes, API contracts, and specific interactions. Avoid file paths or code snippets.

Testing Decisions

Describe what makes a good test, which modules will be tested, and any prior art for the tests.

Out of Scope

List what is explicitly not included in this PRD.

Further Notes

Add any additional context or considerations.

7. Submit as a GitHub Issue

Once complete, submit your PRD as a GitHub issue for visibility and collaboration.

---

Summary: A great PRD is the foundation of a successful project. By following this structured, collaborative approach, you’ll ensure your team is aligned and your product is built on solid ground.

Reference:

• How to Write a PRD by Matt Pocock