# Free PRD template

This is a free product requirements document (PRD) template in Markdown, with a guidance comment under every section. Use it when a feature is big enough that product, design and engineering need one written agreement on the problem, the evidence, the scope and how you will know it worked, before anyone starts building.

Updated14 November 2026

## How do you use this template?

- Copy the template below into your doc tool, wiki or repository. It is plain Markdown, so it pastes cleanly into Notion, Confluence, Google Docs or a .md file.
- Fill in **Problem** and **Evidence** first, before any solution. If you cannot fill in Evidence, do more research before writing the rest.
- Write **Non-goals** early. It is easier to agree on what you are not doing before the requirements list grows.
- Number every requirement and give each P0 and P1 testable acceptance criteria.
- Review with design and engineering, record open questions with owners, and delete the guidance comments once a section is done.

## The PRD template

prd-template.md

```
# PRD: [Feature name]

| Field | Value |
|---|---|
| Owner | [PM name] |
| Reviewers | [Design lead], [Engineering lead] |
| Status | Draft / In review / Approved / Shipped |
| Last updated | [YYYY-MM-DD] |
| Links | [Design file], [Research], [Epic or project] |

## 1. Summary

## 2. Problem

## 3. Evidence

| Evidence | Source | Strength |
|---|---|---|
| "[Verbatim customer quote]" | [Interview 4, Finance lead, 2026-10-02] | Repeated across 4 of 8 interviews |
| [Ticket volume or usage data] | [Support export, Q3] | Behavioral |

## 4. Target users

- Primary:
- Secondary:
- Not for:

## 5. Goals and success metrics

| Goal | Metric | Baseline | Target | Measured when |
|---|---|---|---|---|
| | | | | |

## 6. Non-goals

-

## 7. User flows

1.
2.
3.

Edge cases:
-

## 8. Requirements

| ID | Requirement | Priority | Acceptance criteria |
|---|---|---|---|
| REQ-001 | | P0 | Given ..., when ..., then ... |
| REQ-002 | | P1 | |

## 9. Non-functional requirements

-

## 10. Design

## 11. Dependencies and risks

| Risk or dependency | Impact if it goes wrong | Mitigation |
|---|---|---|
| | | |

## 12. Assumptions and open questions

| ID | Assumption or question | Impact if wrong | Owner | Due |
|---|---|---|---|---|
| ASM-001 | | High / Medium / Low | | |

## 13. Launch plan

## 14. Changelog

- [YYYY-MM-DD] Created.

```

## Common mistakes when writing a PRD

- **Describing the feature in the Problem section.** That rules out better solutions before anyone considers them.
- **Leaving Evidence empty.** Without it, every review reopens whether the problem is real.
- **Untestable requirements.** "Fast", "simple" and "intuitive" are not acceptance criteria.
- **No edge cases.** Empty states, errors and permissions are where most rework comes from.
- **Letting it go stale.** Update the changelog when decisions change, or people stop trusting the document.

## How Praxiom AI fills this in for you

Praxiom AI drafts a PRD from your synthesized research, using insights and their source quotes as the evidence. You edit the draft in the app, export it to PDF or Markdown, and split it into scoped tickets in Linear, Jira, GitHub. See [PRD generation](https://www.praxiomai.xyz/use-cases/prd-generation) or [sign up](https://app.praxiomai.xyz/sign-up).

## Frequently asked questions

### Is this PRD template free?

Yes. Copy it, change it and use it for any product, with no sign-up.

### What sections should every PRD have?

At minimum: problem, evidence, target users, goals with success metrics, non-goals, user flows and requirements with acceptance criteria. Risks, open questions and a launch plan matter more as the feature gets bigger.

### Can I hand this PRD to an AI coding agent?

It is a good start, but agents need more precision than people do. Use the [spec packet template](https://www.praxiomai.xyz/templates/spec-packet-template) to add constraints, a test plan and likely files, and to resolve open questions first.

### How is a PRD different from a one-pager?

A one-pager pitches the problem and the bet to get agreement to proceed. A PRD defines what will be built in enough detail to build it. Many teams write the one-pager first, then expand it into this template.

Run your product discovery on autopilot.

Bring your interviews, tickets and surveys. Get scored insights, a PRD and tickets.

[Sign up](https://app.praxiomai.xyz/sign-up)[See pricing](https://www.praxiomai.xyz/pricing)

Source: https://www.praxiomai.xyz/templates/prd-template
