PRD (Full): Feature / product name

Enterprise-grade PRD – the heavyweight variant of prd.md. Use when the feature crosses multiple teams, has legal/security surface, or needs explicit sign-off. For lean teams, prd.md is enough.

Field	Value
Doc status	Draft / In review / Approved / Implemented
Author	@pm
Approvers	@eng-lead, @design-lead, @legal
Stakeholders	All teams affected
Created	YYYY-MM-DD
Target release	vX.Y
Related	Epic link, design link, tech spec link

1. Executive summary

Two paragraphs a VP can read: the problem, the proposal, the expected outcome, the cost.

2. Problem statement

2.1 The problem

What is broken or missing today. Evidence:

• User research finding (link)
• Support data: N tickets/quarter on X
• Metric showing the gap

2.2 Who has this problem

Persona	Description	Frequency hit
Persona A	...	daily
Persona B	...	weekly

2.3 Cost of doing nothing

Quantified downside if we do not act.

3. Goals & success metrics

Goal	Metric	Baseline	Target	How measured
Primary	Activation rate	N%	N%	Analytics event X
Secondary	Time-to-value	N min	N min	Funnel
Guardrail	Error rate	N%	<= N%	Must not regress

4. Non-goals

Explicitly out of scope – the scope-creep firewall.

5. Solution overview

One-paragraph description of what we will build.

6. Detailed requirements

6.1 Functional requirements

ID	Requirement	Priority	Acceptance criteria
FR-1	The system shall ...	P0	Given/when/then
FR-2	...	P1	...
FR-3	...	P2	...

6.2 User experience

flowchart TD
    A[Entry point] --> B{Decision}
    B -->|path 1| C[State]
    B -->|path 2| D[State]

• Key screens: description + link to mocks
• Empty states, loading states, error states
• Accessibility requirements: WCAG target, keyboard nav, SR labels
• i18n: strings externalized, RTL considerations

6.3 Non-functional requirements

Category	Requirement
Performance	p95 < Nms under defined load
Scale	N concurrent users, N records
Availability	target
Compatibility	browsers/OS matrix

6.4 Security & privacy

• New data collected and its classification
• Consent requirements
• Threat considerations
• Compliance (GDPR/CCPA/etc) implications

6.5 Analytics / telemetry

Event	Trigger	Property
event_name	user action	dimension

7. Dependencies

• Team/system dependencies
• External vendors
• What must land first

8. Rollout plan

Phase	Scope	Gate
Internal dogfood	team	sign-off
Beta N%	cohort	metrics review
GA	all	–

Rollback plan and owner.

9. Open questions & risks

Item	Type	Owner	Due
Question	open	@name	date
Risk	risk	@name	–

10. Appendix

• Research links
• Glossary
• Revision history