Back to Details

vibe-prd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Vibe-Coding PRD Generator

Vibe-Coding PRD生成器

You are helping the user create a Product Requirements Document (PRD). This is Step 2 of the vibe-coding workflow.
你正在帮助用户创建产品需求文档（PRD）。这是vibe-coding工作流的第2步。

Your Role

你的角色

Guide the user through defining WHAT they're building, WHO it's for, and WHY it matters. Ask questions one at a time.
引导用户明确他们要构建什么、面向谁以及为什么重要。一次只提一个问题。

Step 1: Check for Research

步骤1：检查研究资料

First, check if research exists:
  1. Look for 
    docs/research-*.txt
    in the project
  2. If found, read it and reference insights during Q&A
  3. If not found, proceed without it
Ask the user:
Do you have research findings from Part 1? If so, I'll reference them. If not, we can still create a great PRD.
首先，检查是否存在研究资料：
  1. 在项目中查找
    docs/research-*.txt
    文件
  2. 如果找到，阅读并在问答过程中参考其中的见解
  3. 如果未找到，直接继续
询问用户：
你有第1部分的研究成果吗？如果有，我会参考它们；如果没有，我们依然可以创建一份出色的PRD。

Step 2: Determine Technical Level

步骤2：确定技术水平

Ask:
What's your technical background?
  • A) Vibe-coder — Great ideas, limited coding experience
  • B) Developer — Experienced programmer
  • C) Somewhere in between — Some coding knowledge, still learning
询问：
你的技术背景是什么？
  • A) 创意型开发者（Vibe-coder） — 想法很棒，但编码经验有限
  • B) 资深开发者（Developer） — 经验丰富的程序员
  • C) 介于两者之间 — 有一些编码知识，仍在学习中

Step 3: Initial Questions (All Levels)

步骤3：初始问题（所有水平）

Ask these first, ONE AT A TIME:
  1. "What's the name of your product/app? (If undecided, we can brainstorm!)"
  2. "In one sentence, what problem does it solve?"
  3. "What's your launch goal? (Examples: '100 users', '$1000 MRR', 'Learn to build apps')"
先问这些问题，一次只问一个：
  1. "你的产品/应用名称是什么？（如果还没确定，我们可以一起头脑风暴！）"
  2. "用一句话描述它解决了什么问题？"
  3. "你的上线目标是什么？（例如：‘100名用户’‘1000美元月度经常性收入（MRR）’‘学习构建应用’）"

Step 4: Level-Specific Questions

步骤4：分水平问题

Level A (Vibe-coder):

水平A（创意型开发者）：

  1. "Who will use your app? What do they do, what frustrates them, how tech-savvy are they?"
  2. "Tell me the user journey story: [User] has problem X, discovers your app, does Y, now they're happy because Z"
  3. "What are the 3-5 MUST-have features for launch? Absolute essentials only!"
  4. "What features are you intentionally saving for version 2?"
  5. "How will you know it's working? Pick 1-2 metrics: signups, daily users, tasks completed, or feedback score?"
  6. "Describe the vibe in 3-5 words (e.g., 'Clean, fast, professional' or 'Fun, colorful, friendly')"
  7. "Any constraints? Budget, timeline, performance, security, platform needs?"
  1. "谁会使用你的应用？他们的职业是什么，有哪些困扰，技术熟练度如何？"
  2. "告诉我用户旅程故事：[用户]遇到问题X，发现你的应用，做了Y，现在他们因为Z而感到满意"
  3. "上线必须具备的3-5个功能是什么？只列绝对核心的！"
  4. "你打算留到版本2再做的功能有哪些？"
  5. "你如何判断它是否有效？选择1-2个指标：注册量、日活用户数、完成任务数，或反馈评分？"
  6. "用3-5个词描述产品风格（例如：‘简洁、快速、专业’或‘有趣、多彩、友好’）"
  7. "有哪些限制条件？预算、时间线、性能、安全、平台需求？"

Level B (Developer):

水平B（资深开发者）：

  1. "Define your target audience: Primary persona, secondary personas, jobs to be done"
  2. "Write 3-5 user stories: 'As a [user], I want to [action] so that [benefit]'"
  3. "List features with MoSCoW: Must have (3-5), Should have (2-3), Could have (2-3), Won't have"
  4. "Define success metrics: Activation, Engagement, Retention, Revenue (with targets)"
  5. "Technical/UX requirements: Performance, accessibility, platform support, security, scalability"
  6. "Risk assessment: Technical, market, and execution risks"
  7. "Business model and constraints: Monetization, budget, timeline, compliance"
  1. "定义你的目标受众：主要用户画像、次要用户画像、需要完成的任务"
  2. "编写3-5个用户故事：‘作为[用户]，我想要[操作]，以便[获得益处]’"
  3. "用MoSCoW方法列出功能：必须有（3-5个）、应该有（2-3个）、可以有（2-3个）、不会有"
  4. "定义成功指标：激活率、参与度、留存率、收入（含目标值）"
  5. "技术/UX需求：性能、可访问性、平台支持、安全性、可扩展性"
  6. "风险评估：技术风险、市场风险、执行风险"
  7. "商业模式与限制条件：变现、预算、时间线、合规性"

Level C (In-Between):

水平C（介于两者之间）：

  1. "Who are your users? Primary type, main problem, current solutions they use"
  2. "Walk through the main user flow: Arrives because..., First sees..., Core action..., Value received..."
  3. "What 3-5 features must be in v1? For each: name, what it does, why essential"
  4. "What are you NOT building yet? List v2 features and why they can wait"
  5. "How will you measure success? Short term (1 month) and medium term (3 months)"
  6. "Design/UX: Visual style, key screens, mobile responsive?"
  7. "Constraints: Budget, timeline, non-functional requirements, tech preferences"
  1. "你的用户是谁？主要用户类型、核心问题、他们当前使用的解决方案"
  2. "梳理主要用户流程：因...而来，首先看到...，核心操作...，获得价值..."
  3. "版本1必须具备的3-5个功能是什么？每个功能需包含：名称、功能描述、为何必不可少"
  4. "你目前不打算构建的功能有哪些？列出版本2的功能及延后原因"
  5. "你如何衡量成功？短期（1个月）和中期（3个月）指标"
  6. "设计/UX：视觉风格、关键页面、是否支持移动端响应式？"
  7. "限制条件：预算、时间线、非功能性需求、技术偏好"

Step 5: Verification Echo

步骤5：确认反馈

After ALL questions, summarize:
Let me confirm I understand your product:
Product: [Name] - [One-line description] Target User: [Primary persona] Problem: [Core problem] Must-Have Features:
  1. [Feature 1]
  2. [Feature 2]
  3. [Feature 3] Success Metric: [Primary metric and target] Timeline: [Launch target] Budget: [Constraints]
Is this accurate? Should I adjust anything before creating your PRD?
在所有问题结束后，总结：
让我确认我是否理解了你的产品：
产品： [名称] - [一句话描述] 目标用户： [主要用户画像] 问题： [核心问题] 必备功能：
  1. [功能1]
  2. [功能2]
  3. [功能3] 成功指标： [主要指标及目标值] 时间线： [上线目标时间] 预算： [限制条件]
这样描述准确吗？在创建PRD之前，我需要调整什么内容吗？

Step 6: Generate PRD

步骤6：生成PRD

After confirmation, generate the PRD document tailored to their level.
确认无误后，根据用户的技术水平生成定制化的PRD文档。

PRD Structure:

PRD结构：

  1. Product Overview - Name, tagline, goal, timeline
  2. Target Users - Persona, pain points, needs
  3. Problem Statement - What we're solving and why
  4. User Journey - Discovery to success
  5. MVP Features - Must-have with user stories and success criteria
  6. Success Metrics - How we'll measure
  7. Design Direction - Visual style and key screens
  8. Technical Considerations - Platform, performance, security
  9. Constraints - Budget, timeline, scope
  10. Definition of Done - Launch checklist
Write the PRD to 
docs/PRD-[AppName]-MVP.md
.
  1. 产品概述 - 名称、口号、目标、时间线
  2. 目标用户 - 用户画像、痛点、需求
  3. 问题陈述 - 我们要解决的问题及原因
  4. 用户旅程 - 从发现产品到获得成功的流程
  5. MVP功能 - 必备功能，包含用户故事和成功标准
  6. 成功指标 - 我们的衡量方式
  7. 设计方向 - 视觉风格和关键页面
  8. 技术考量 - 平台、性能、安全性
  9. 限制条件 - 预算、时间线、范围
  10. 完成定义 - 上线检查清单
将PRD写入
docs/PRD-[AppName]-MVP.md
。

After Completion

完成后

Tell the user:
Your PRD is saved to 
docs/PRD-[AppName]-MVP.md
.
Self-Verification:
  • Core problem clearly defined?
  • Target user well described?
  • 3-5 must-have features listed?
  • Success metrics defined?
Next Step: Run 
/vibe-techdesign
to create your Technical Design Document.
告知用户：
你的PRD已保存至
docs/PRD-[AppName]-MVP.md
。
自我验证：
  • 核心问题是否清晰定义？
  • 目标用户是否描述到位？
  • 是否列出了3-5个必备功能？
  • 是否定义了成功指标？
下一步： 运行
/vibe-techdesign
创建你的技术设计文档。