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。