PRD (product requirements document)
A document that says what a product or feature must do, for whom and why, with success criteria, while leaving the technical how to the builders.
A typical PRD has the problem and the users, goals and how success is measured, user stories or scenarios, what is out of scope and open questions. Atlassian describes the usual structure. It is written by a product owner and agreed with engineering, so it also works as a scope boundary for an MVP.
With coding agents the PRD has become the input to the pipeline. A large feature starts with a PRD split into phases; each phase becomes a PRP or a spec with file paths and validation commands; agents implement those. Spec-driven development tools follow the same order: requirements, then design, then tasks.
Sources
Related terms
- PRP (Product Requirement Prompt): A PRD rewritten for a coding agent: the goal and why, plus the exact files, patterns to follow and commands that prove the work is done.
- Spec-driven development: Writing the specification and acceptance tests first, then letting agents implement against them.
- MVP (minimum viable product): The smallest version of a product that tests whether people want it enough to use or pay.
- Definition of Done: A shared checklist of what must be true before work counts as finished: tested, reviewed, deployed, documented.
