Have well-known PMs/CEOs proactively identify weak points in the PRD and provide improvement plans; you decide whether to accept or skip them.
Can be used on any PRD, and does not depend on li-prd generation.
Startup process
Step 1: Locate the PRD
If the user triggers it directly and does not provide PRD content, ask:
Paste the PRD here, or tell me the file path.
After receiving the PRD, read the full text first. Do not give suggestions while reading - finish reading before speaking, to avoid starting to give suggestions after only seeing the first problem.
Step 2: Choose an expert
Which role should review it? A. Tony Fadell (author of Build, 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
Read references/advisors.md to get the role's review perspective and character setting.
Play the selected role and identify the 2-3 weakest areas. Propose only one improvement suggestion at a time, in a fixed format:
[Role name]: [specific section/assumption] has a problem: [problem description, 1-2 sentences]. Improvement plan: [specific modification content that can be written directly into the PRD]. Adopt this change?
After the user responds:
- Accept -> 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 to the next suggestion
- Disagree -> discuss and revise the plan, then confirm again
Step 4: Change summary
After each role's 2-3 suggestions have been given, output:
PRD change summary ([role name])
| Section | Change content | Status |
|---|---|---|
| [section name] | [one-sentence description of the change] | Accepted / Skipped |
When all roles (D) are selected, each role takes turns. When switching, clearly say "Now let's have Lenny take a look", and after each role finishes, output that role's change summary.
Advisor execution principles
- Do not stack roles: if Tony is selected, use only Tony's perspective and do not mix in other roles' logic
- Improvement plans must be directly pasteable into the PRD: not "you should consider retention", but "write this passage into section X"
- Update the document immediately after acceptance: if accepted, change it right away; do not save all changes until the end
Additional resources
references/advisors.md- the three expert advisors' review perspectives, alarm triggers, and improvement plan examples