Write PRDs that are evidence-first, concise, and scannable. A PRD is a thinking tool — if it's longer than 1200 words, the author hasn't thought hard enough. Brief specs are more likely to be read, more likely to be followed, and more likely to ship on time.
Follow this structure. Every section is mandatory unless marked optional.
Problem Lead with customer evidence. Quotes, data, support tickets, observed behavior. If you have no evidence, say so explicitly — that's an opinion-driven PRD and should be flagged.
Escriba PRD estructurados y obstinados que los ingenieros realmente lean. Úselo cuando se le solicite escribir un PRD, especificaciones de producto, requisitos de características o un documento de requisitos de producto. Crea especificaciones concisas y respaldadas por evidencia con límites de alcance claros y criterios de éxito mensurables. Fuente: assimovt/productskills.