PRD Writer

---

name: prd-writer description: Write strategy-oriented Product Requirements Documents (PRDs) for AI product managers. Use when: (1) drafting a new PRD or strategy doc, (2) structuring a feature proposal with strategy rationale, (3) writing requirement docs that emphasize "why" over "how", (4) turning raw product ideas into structured requirement documents. NOT for: purely technical specs, engineering tickets, or UI copy.

---

PRD Writer

Produce structured, strategy-first PRDs for AI product managers.

Core Philosophy

Strategy PRDs answer why before what. Every section should connect features back to business goals and user outcomes. Avoid feature laundry lists; prioritize decision rationale.

Standard PRD Structure

Use this structure unless the user specifies otherwise:

1. 背景与目标 (Background & Goals)

产品背景：当前现状和痛点

战略目标：本需求解决什么业务问题

成功指标：可量化的 KPI / OKR

2. 用户与场景 (Users & Scenarios)

目标用户群体（细分）

核心使用场景（用户故事格式）

用户旅程关键节点

3. 产品方案 (Solution)

核心功能列表（MoSCoW 优先级）

关键交互逻辑

边界与限制（Not in scope）

4. 策略设计 (Strategy Design)

算法/策略说明（AI 产品重点）

数据依赖与冷启动策略

A/B 测试方案

5. 技术依赖 (Technical Dependencies)

依赖系统/接口

数据需求

性能要求

6. 风险与降级 (Risks & Fallback)

主要风险点

降级方案

7. 里程碑 (Milestones)

分阶段交付计划

Writing Guidelines

用中文撰写，除非用户指定英文

策略逻辑要显式说明，不要隐含在功能描述里

每个功能点标注优先级：P0/P1/P2 或 Must/Should/Could

AI 策略类需求必须包含：输入信号、模型/策略逻辑、输出形式、兜底规则

Reference Files

references/prd-template.md — 完整 PRD 模板（Markdown）

references/strategy-patterns.md — 常见 AI 产品策略模式（推荐、排序、召回、意图识别等）

Read references when: user asks for a full template, or when the PRD involves AI/ML strategy components.