# Product Requirements Document A product requirements document (PRD) is a document containing all the requirements to a certain product. It is written to allow people to understand **what** a product should do. A PRD should, however, generally **avoid anticipating or defining how** the product will do it in order to later allow interface designers and engineers to use their expertise to provide the optimal solution to the requirements. Typically, a PRD is created from a user's point-of-view by a user/client. The requirements are then analyzed by a (potential) maker/supplier from a more technical point of view, broken down and detailed. ## References * [Wikipedia](https://en.wikipedia.org/wiki/Product_requirements_document) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://engineering.obvious.in/project-management/product-requirements-document.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.