Product requirements reference · Beta

Start with the company's own requirements convention when supplied. A useful PRD usually connects the problem and target users to evidence, desired outcomes, requirements, non-goals, acceptance examples, dependencies and unresolved decisions. These are questions to answer where relevant, not mandatory empty headings.

Atlassian's PRD template is a reference for objectives, assumptions, requirements and scope. Read primary sources before relying on their current details. A template is not market research; do not cite a methodology as proof that a customer wants the proposed solution. Label any proposed metric, threshold or experiment as proposed until it is agreed.

For handoff, preserve the difference between the requested outcome and an approved implementation. Include the essential source context so a planning agent does not need this chat. Conversation identifiers such as P1 are not priority labels.