PRD Creation Assistant

Stage 1: Determine PRD Type

1. Ask about PRD Type: Use the AskUserQuestion tool to inquire which type of PRD the user needs
   • Full PRD (Recommended): Includes all standard sections, suitable for complex projects and key features
   • Condensed PRD: Only includes core sections (Problem Statement, Success Metrics, Core Features, Timeline), suitable for rapid iteration of small features
2. Record Selection: Based on the user's choice, confirm the subsequent chapter structure for generation

Stage 2: Collect Information

Basic Information (Required for Both Full and Condensed PRDs)

1. Product/Feature Name
   • Question: "Please provide the name of the product or feature"
   • Example Answers: "Smart Meeting Assistant", "User Profile System 2.0"
2. Problem Statement
   • Question: "What problem does this product/feature solve? What pain points are users currently facing?"
   • Tip: Please describe user scenarios and pain points in detail
   • Example Answer: "Sales teams spend a lot of time organizing meeting minutes and action items after meetings, leading to low efficiency"
3. Target Users
   • Question: "Who are the main users of this product/feature? Please describe the user persona"
   • Example Answer: "Sales managers at B2B SaaS companies, aged 28-40, who need to attend client meetings frequently"
4. Core Objective
   • Question: "What is the core objective of this product/feature? (Please be as specific as possible, aligning with the SMART principle)"
   • Tip: SMART = Specific, Measurable, Achievable, Relevant, Time-bound
   • Example Answer: "Reduce the average post-meeting organization time for sales teams from 30 minutes to 5 minutes within 3 months"
5. Success Metrics
   • Question: "How will the success of this product/feature be measured? Please list key performance indicators (KPIs)"
   • Example Answer: "Meeting minutes generation time, user satisfaction score, weekly active users, action item completion rate"
6. Core Features
   • Question: "Please list the 3-5 most important core features that this product/feature needs to include"
   • Example Answer: "Real-time speech-to-text, automatic action item extraction, meeting summary generation, CRM integration"
7. Timeline
   • Question: "What is the expected release timeline or key milestones?"
   • Example Answer: "MVP development: 2 months, Beta testing: 1 month, official launch after 3 months"

Additional Information for Full PRD

1. User Stories/Scenarios
   • Question: "Please describe 2-3 typical user usage scenarios or user stories"
   • Example Answer: "Scenario 1: After a client meeting, the sales manager opens the app to automatically generate meeting minutes and extract next-step action items"
2. Out of Scope
   • Question: "Which features or requirements are explicitly out of scope for this project?"
   • Example Answer: "Does not support video recording, does not include AI-powered customer sentiment analysis"
3. Stakeholders
   • Question: "Who are the key stakeholders for this project? (Product Owner, Development Lead, Designer, etc.)"
   • Example Answer: "Product Owner: Zhang San, Technical Lead: Li Si, Designer: Wang Wu"
4. Risks and Dependencies
   • Question: "What potential risks or external dependencies need to be noted?"
   • Example Answer: "Depends on the stability of third-party speech recognition APIs, requires integration with existing CRM systems"
5. Open Questions
   • Question: "What current questions or doubts need further discussion?"
   • Example Answer: "Need to confirm data privacy compliance requirements, need to evaluate the priority of multilingual support"

Stage 3: Generate PRD Document

1. Select Template: Use the corresponding template based on the user's choice in Stage 1
   • Full Version: Refer to

     references/prd-template-full.md

   • Condensed Version: Refer to

     references/prd-template-brief.md

2. Fill in Content:
   • Populate each section with the collected information
   • Ensure professional, clear, and concise language
   • Write all content in Chinese
   • Follow best practice principles (refer to

     references/prd-best-practices.md

     )
3. Data-Driven:
   • Include specific data or research support in the problem statement
   • Apply the SMART principle in objectives
   • Define quantifiable metrics in success indicators
4. Format Specifications:
   • Use Markdown format
   • Clear hierarchical section headings (# ## ###)
   • Use lists, tables, and other formats appropriately

Stage 4: Validation and Saving

Step 4.1: Completeness Check

• Condensed Version Required: Problem Statement, Success Metrics, Core Features, Timeline
• Full Version Required: All condensed version sections + Background, Target Users, User Stories, Out of Scope, Stakeholders, Risks & Dependencies, Open Questions

Step 4.2: SMART Objective Validation

• S (Specific): Is the objective specific and clear?
• M (Measurable): Is the objective quantifiable?
• A (Achievable): Is the objective attainable?
• R (Relevant): Is the objective relevant to the business?
• T (Time-bound): Does the objective have a clear time limit?

Step 4.3: Content Quality Check

• Is the problem statement clear and supported by data?
• Are the success metrics specific and measurable?
• Is the feature description complete and executable?
• Is the timeline reasonable?
• Are there any obvious omissions or contradictions?

Step 4.4: Save File

1. Generate File Name:
   • Format:

     PRD-[Product Name]-[Date].md

   • Example:

     PRD-智能会议助手-20260128.md

   • Date Format: YYYYMMDD
2. Determine Save Path:
   • Default Path: Current working directory
   • If

     docs/

     or

     prd/

     directories exist, prioritize saving to these directories
3. Save Using Write Tool:
   • Write the generated PRD content to the file
   • Use UTF-8 encoding to ensure correct display of Chinese characters
4. Confirm Saving:
   • Report the file save path to the user
   • Provide a file summary (number of sections, total word count, etc.)

Quality Principles

• Data-Driven: Use specific data and user research to support the problem statement
• SMART Objectives: Ensure objectives are Specific, Measurable, Achievable, Relevant, and Time-bound
• Concise and Clear: Follow the 2026 PRD trend of conciseness, avoid lengthy content
• Executability: Feature descriptions should be clear enough for the development team to directly understand and implement
• Collaboration-Oriented: PRD is a collaboration tool, not an authoritative order; the tone should promote discussion

• Use professional product management terminology
• Write all content in Chinese
• Avoid vague terms (e.g., "approximately", "maybe", "try to")
• Use active voice and clear verbs

Supporting Files

• references/prd-template-full.md

  — Full version PRD template structure

• references/prd-template-brief.md

  — Condensed version PRD template structure

• references/prd-best-practices.md

  — PRD Best Practices Guide (2026)

• references/prd-examples.md

  — High-quality PRD examples

Notes

• All PRD content must be written in Chinese
• Prioritize collecting information by asking questions one by one to ensure each question is fully answered
• Ensure all required information is collected completely before generating the PRD
• When issues are found during the validation stage, provide specific improvement suggestions instead of regenerating the entire document
• Use the Chinese product name in the file name to ensure consistency with the PRD content