# Product requirements document

Concept · [Product](https://ecosystem.samcarlton.com/product)

Also called: PRD, PRDs, product requirements, product spec

A document that explains what a product or feature should do, for whom and why, so the team agrees before building. [AI coding tools](https://ecosystem.samcarlton.com/coding-agent) often work from one too.

**For example:** Before a sprint, the [founder](https://ecosystem.samcarlton.com/founder) writes a two-page PRD for the invoicing feature with goals, [user stories](https://ecosystem.samcarlton.com/user-story) and what is [out of scope](https://ecosystem.samcarlton.com/scope).

## Connects to (6)

- [Technical requirements document](https://ecosystem.samcarlton.com/technical-requirements-document): A document that explains how a feature will be built: the systems, data and technical choices.
- [User story](https://ecosystem.samcarlton.com/user-story): One short sentence describing something a user needs to do and why, written from their point of view.
- [Scope](https://ecosystem.samcarlton.com/scope): The agreed list of what a project will include and what it will not.
- [Roadmap](https://ecosystem.samcarlton.com/roadmap): A plan that shows what you intend to build and in roughly what order.
- [Spec](https://ecosystem.samcarlton.com/spec): A written description of what is being built and why, for work too big to finish in one session.
- [Product manager vs program manager](https://ecosystem.samcarlton.com/product-vs-program-manager): Both are called PM.

Map view: https://ecosystem.samcarlton.com/product-requirements-document