prd-writing

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.

编写工程师实际阅读的结构化、固执己见的 PRD。当要求编写 PRD、产品规格、功能需求或产品需求文档时使用。创建简洁、有证据支持的规范，具有清晰的范围边界和可衡量的成功标准。 来源：assimovt/productskills。