Back to Details

bmad-product-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Product Requirements Skill

产品需求Skill

When to Invoke

触发时机

Automatically activate this skill when the user:
  • Says "I want to build...", "Let's build...", "Create a..."
  • Asks "Create a PRD", "Write requirements", "Plan this feature"
  • Mentions "product requirements", "PRD", "epic roadmap"
  • Has completed discovery phase and needs formal requirements
  • Is starting a Level 2-4 project requiring structured planning
  • Uses words like: build, create, PRD, requirements, plan, feature, product
Specific trigger phrases:
  • "I want to build [something]"
  • "Create a PRD for [project]"
  • "Plan this feature"
  • "Write the requirements"
  • "What should be in the PRD?"
  • "Break this into epics"
  • "Product requirements for [project]"
Prerequisites check:
  • If Level 3-4 project: verify analysis phase complete (discovery brief exists)
  • If missing analysis: recommend invoking bmad-discovery-research first
  • If Level 0-1: suggest OpenSpec workflow instead
Do NOT invoke when:
  • User is still exploring/brainstorming (use bmad-discovery-research first)
  • User is ready for architecture (use bmad-architecture-design instead)
  • User wants to code directly (check if prerequisites exist first)
  • Project is Level 0-1 simple change (use OpenSpec)
当用户出现以下情况时，自动激活该Skill：
  • 说出“我想要构建...”、“我们来构建...”、“创建一个...”这类表述
  • 提出“创建PRD”、“撰写需求文档”、“规划该功能”这类请求
  • 提及“产品需求”、“PRD”、“Epic路线图”
  • 已完成发现阶段，需要正式的需求文档
  • 启动需要结构化规划的2-4级项目
  • 使用了构建、创建、PRD、需求、规划、功能、产品这类词汇
具体触发短语：
  • "我想要构建[某事物]"
  • "为[项目]创建PRD"
  • "规划该功能"
  • "撰写需求文档"
  • "PRD中应该包含哪些内容？"
  • "将其拆分为Epic"
  • "[项目]的产品需求"
前置条件检查：
  • 若为3-4级项目：需确认分析阶段已完成（即存在发现简报）
  • 若缺少分析内容：建议先调用bmad-discovery-research
  • 若为0-1级项目：建议改用OpenSpec工作流
请勿触发的场景：
  • 用户仍处于探索/头脑风暴阶段（请先使用bmad-discovery-research）
  • 用户已准备好进行架构设计（请改用bmad-architecture-design）
  • 用户想要直接编码（请先检查是否满足前置条件）
  • 项目为0-1级简单变更（请使用OpenSpec）

Mission

核心目标

Transform validated discovery insights into a production-ready Product Requirements Document (PRD) and epic roadmap that align stakeholders and prepare downstream architecture, UX, and delivery work.
将经过验证的发现阶段洞察转化为可投入使用的Product Requirements Document（PRD）和Epic路线图，对齐各方利益相关者，为后续的架构设计、UX设计和交付工作做好准备。

Inputs Required

所需输入

  • business_goal: clear outcome statement tied to measurable success metrics
  • stakeholders: decision makers plus their approvals or open concerns
  • constraints: technical, regulatory, financial, or timeline guardrails
  • discovery_artifacts: briefs, research memos, or notes from the discovery-analysis skill
If any input is missing or stale, pause and request the exact artifact before proceeding.
  • business_goal：清晰的成果陈述，需关联可衡量的成功指标
  • stakeholders：决策者及其批准意见或未解决的顾虑
  • constraints：技术、合规、财务或时间线方面的约束条件
  • discovery_artifacts：来自发现分析Skill的简报、研究备忘录或笔记
若任何输入缺失或已过时，请暂停流程，先获取所需的具体资料再继续。

Outputs

输出内容

Produce two markdown artifacts aligned to the templates in 
assets/
:
  1. PRD.md
    populated from 
    assets/prd-template.md.template
  2. epics.md
    populated from 
    assets/epic-roadmap-template.md.template
Deliverables must be written to the project documentation folder (default 
docs/
) and summarized for the requestor.
生成两个与
assets/
目录下模板对齐的Markdown文件：
  1. 基于
    assets/prd-template.md.template
    生成的
    PRD.md
  2. 基于
    assets/epic-roadmap-template.md.template
    生成的
    epics.md
交付物必须写入项目文档目录（默认路径为
docs/
），并向请求者提供摘要。

Process

执行流程

  1. Validate readiness using the gate in 
    CHECKLIST.md
    .
  2. Review discovery inputs and clarify remaining unknowns.
  3. Map goals, scope, and constraints into structured PRD sections.
  4. Prioritize epics, sequencing, and acceptance signals for delivery.
  5. Run 
    scripts/generate_prd.py
    when structured data exists; otherwise compose outputs manually following templates.
  6. Apply the quality checklist before returning deliverables and recommended next steps.
  1. 使用
    CHECKLIST.md
    中的检查项验证是否已准备就绪。
  2. 审核发现阶段的输入内容，澄清剩余的未知事项。
  3. 将目标、范围和约束条件映射到结构化的PRD章节中。
  4. 对交付所需的Epic、执行顺序和验收标准进行优先级排序。
  5. 若存在结构化数据，则运行
    scripts/generate_prd.py
    ；否则按照模板手动撰写输出内容。
  6. 在返回交付物和推荐的后续步骤前，执行质量检查清单中的内容。

Quality Gates

质量检查关口

Confirm every item in 
CHECKLIST.md
is satisfied before delivering the PRD package. Stop and fix any unmet criteria.
在交付PRD包之前，需确认
CHECKLIST.md
中的所有项均已满足。若有未达标的项，请暂停并修复。

Error Handling

错误处理

If prerequisites are missing or contradictions surface:
  • Identify which required input is absent and why it blocks progress.
  • Provide a minimal list of follow-up questions or stakeholders needed.
  • Recommend re-engaging the discovery-analysis skill or orchestrator when scope is unclear.
若前置条件缺失或出现矛盾：
  • 明确指出缺失的必要输入项及其对流程的阻碍原因。
  • 提供最精简的后续问题列表或所需对接的利益相关者。
  • 若范围不明确，建议重新调用发现分析Skill或编排器。