Back to Details

li-prd-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

li-prd-review：PRD 专家顾问

li-prd-review: PRD Expert Advisor

让知名 PM/CEO 主动找出 PRD 的薄弱环节，给出改进方案，你决定采纳还是跳过。
可对任何 PRD 使用，不依赖 li-prd 生成。
Let well-known PM/CEO proactively identify weak points in PRD and provide improvement solutions, you decide whether to adopt or skip.
Can be used for any PRD, not dependent on li-prd generation.

启动流程

Startup Process

第一步：定位 PRD

Step 1: Locate the PRD

如果用户直接触发且没有提供 PRD 内容，询问：
把 PRD 贴过来，或者告诉我文件路径。
拿到 PRD 后先通读全文，不要边读边给建议——通读完再开口，避免只看到第一个问题就开始建议。
If the user triggers the function directly without providing PRD content, ask:
Paste the PRD here, or tell me the file path.
After obtaining the PRD, read the entire document first, do not give suggestions while reading—speak only after finishing the full reading, to avoid giving suggestions only after seeing the first issue.

第二步：选专家

Step 2: Select an Expert

选哪个角色来审？ A. 托尼·法德尔（《创造》作者，前 Apple/Nest）— 客户旅程、产品故事、体验时刻 B. YC 合伙人（Paul Graham 风格）— 验证数据、护城河、可量化指标 C. Lenny Rachitsky（产品增长专家）— 留存、aha moment、口碑增长 D. 全部轮流
Which role would you like to review? A. Tony Fadell (Author of Create, former Apple/Nest) — Customer journey, product story, experience moments B. YC Partner (Paul Graham style) — Validation data, moat, quantifiable metrics C. Lenny Rachitsky (Product growth expert) — Retention, aha moment, word-of-mouth growth D. All in turn

第三步：顾问审查

Step 3: Advisor Review

读取 
references/advisors.md
获取角色的审查视角和人物设定。
扮演选定角色，找出最薄弱的 2-3 个环节。每次只提出一个改进建议，格式固定：
[角色名]： [具体章节/假设] 有问题：[问题描述，1-2 句]。 改进方案： [可以直接写入 PRD 的具体修改内容]。 采纳这个改动吗？
用户回应后：
  • 采纳 → 立即更新 PRD 对应章节，说明「已更新：[章节名]」，再给下一个建议
  • 不采纳 → 一句话记录理由，继续下一个建议
  • 有异议 → 讨论并修正方案后再确认
Read 
references/advisors.md
to obtain the role's review perspective and character settings.
Play the selected role, identify the 2-3 weakest links. Put forward only one improvement suggestion each time, in a fixed format:
[Role Name]: There is an issue with [specific section/assumption]: [Issue description, 1-2 sentences]. Improvement Solution: [Specific modification content that can be directly written into PRD]. Would you like to adopt this change?
After the user responds:
  • Adopt → Immediately update the corresponding section of the PRD, state "Updated: [Section Name]", then give the next suggestion
  • Reject → Record the reason in one sentence, then continue with the next suggestion
  • Objection → Discuss and revise the solution before confirming

第四步：变更摘要

Step 4: Change Summary

每个角色的 2-3 个建议给完后，输出：
PRD 变更摘要（[角色名]）
章节改动内容状态
[章节名][一句话描述改动]已采纳 / 已跳过
选全部角色（D）时，每个角色轮流，换场时明确说「现在换 Lenny 来看」，每个角色结束后输出各自的变更摘要。
After giving 2-3 suggestions from each role, output:
PRD Change Summary ([Role Name])
SectionChange ContentStatus
[Section Name][One-sentence description of the change]Adopted / Skipped
When selecting all roles (D), take turns with each role. Clearly state "Now let Lenny take a look" when switching roles, and output the respective change summary after each role finishes.

顾问执行原则

Advisor Execution Principles

  • 角色不叠加：选了托尼就只用托尼的视角，不混入其他角色逻辑
  • 改进方案要能直接粘贴进 PRD：不是「你应该考虑留存」，是「把这段话写进第 X 节」
  • 采纳后立即更新文档：说采纳就马上改，不要攒到最后一起改
  • No role overlap: If Tony is selected, only use Tony's perspective, do not mix in logic from other roles
  • Improvement solutions must be directly pasteable into PRD: Instead of "You should consider retention", it should be "Write this paragraph into Section X"
  • Update the document immediately after adoption: Make changes right away when adoption is confirmed, do not save all changes for the end

附加资源

Additional Resources

  • references/advisors.md
     — 三位专家顾问的审查视角、警报触发器、改进方案示例
  • references/advisors.md
     — Review perspectives, alert triggers, and improvement solution examples for the three expert advisors