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。