Standard PRD

Purpose

Turn scattered product material into business-first PRDs that are detailed enough to guide implementation without becoming architecture specs.

Core rules

1. Prefer page-level splitting

When the source clearly contains pages, Tabs, screens, dialogs, or drawers:

• generate one overview PRD
• then split PRDs by page or Tab
• keep modal/drawer PRDs separate when they represent distinct business actions

Do not flatten a page-based product into broad capability buckets if the UI already defines page boundaries.

2. Business detail beats summary