Once your brief is solid:
BRIEF:
PRD STRUCTURE:
1. Problem Statement (specific, one user, one scenario)
2. Goals (what changes for the user; what changes for the business)
3. Non-Goals (what this explicitly does not address)
4. User Stories (main flow, then edge cases)
5. Functional Requirements (numbered, testable, specific)
6. Success Metrics (tied to the behavior change, not just engagement)
7. Open Questions (things we still need to decide)
Requirements for the output:
Every functional requirement must be specific enough to test
Non-Goals should be real candidates that someone might expect to be in scope
Success metrics should be measurable within 60 days of launch
Avoid placeholder language like "the system should handle errors appropriately" be specific about what "appropriately" means