Back to Details

bmad-discovery-research

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Discovery Analysis Skill

Discovery Analysis Skill

When to Invoke

触发时机

Automatically activate this skill when the user:
  • Says "I have an idea...", "What if we...", "I'm thinking about..."
  • Asks "Help me think through...", "Can you help me brainstorm...", "Let's explore..."
  • Mentions "new project", "new feature", "explore possibilities"
  • Talks about research, competitive analysis, or market exploration
  • Has vague requirements that need clarification
  • Mentions understanding or documenting an existing project
  • Is starting a Level 3-4 project (complex/novel problems)
  • Uses words like: idea, brainstorm, explore, research, discovery, analyze
Specific trigger phrases:
  • "I have an idea for [something]"
  • "What if we built [something]"
  • "Help me think through [problem]"
  • "Can we explore [opportunity]"
  • "I need to research [topic]"
  • "Document this project"
  • "Understand this codebase"
Do NOT invoke when:
  • User already has a detailed PRD (use bmad-product-planning instead)
  • User is asking for implementation help (use bmad-development-execution instead)
  • User has clear, well-defined requirements (skip to bmad-product-planning)
  • User is asking about workflow status (use main-workflow-router)
  • Project is Level 0-2 and requirements are clear (skip to bmad-product-planning)
当用户出现以下情况时自动激活此Skill：
  • 说出“我有一个想法……”、“如果我们……会怎样”、“我正在考虑……”
  • 询问“帮我梳理一下……”、“你能帮我构思创意吗……”、“我们来探索一下……”
  • 提到“新项目”、“新功能”、“探索可能性”
  • 谈论研究、竞品分析或市场调研
  • 需求模糊需要澄清
  • 提到要理解或记录现有项目
  • 启动3-4级项目（复杂/新颖问题）
  • 使用以下词汇：想法、构思、探索、研究、发现、分析
特定触发短语：
  • “我有一个关于[某事]的想法”
  • “如果我们开发[某物]会怎样”
  • “帮我梳理[问题]”
  • “我们能探索[机会]吗”
  • “我需要研究[主题]”
  • “记录这个项目”
  • “理解这个代码库”
请勿触发的情况：
  • 用户已有详细的PRD（请使用bmad-product-planning）
  • 用户询问实现帮助（请使用bmad-development-execution）
  • 用户需求清晰明确（直接跳转至bmad-product-planning）
  • 用户询问工作流状态（请使用main-workflow-router）
  • 项目为0-2级且需求明确（直接跳转至bmad-product-planning）

Mission

任务目标

Turn vague ideas or problem statements into structured briefs that downstream skills can trust. Identify goals, constraints, risks, and unknowns to inform product planning.
将模糊的想法或问题陈述转化为下游Skill可信赖的结构化简报。明确目标、约束、风险和未知因素，为产品规划提供依据。

Inputs Required

所需输入

  • problem_statement: initial idea, pain, or opportunity description
  • stakeholders: who cares about the outcome and why
  • context_assets: repos, documents, or market references available for analysis
If essential context is missing, gather it before deeper synthesis.
  • problem_statement：初始想法、痛点或机会描述
  • stakeholders：关注结果的相关方及其原因
  • context_assets：可用于分析的代码库、文档或市场参考资料
如果缺少关键背景信息，需先收集再进行深度整合。

Outputs

输出内容

  • Discovery brief following patterns in 
    REFERENCE.md
  • Brainstorm notes (from 
    assets/brainstorm-template.md.template
    )
  • Product brief (from 
    assets/product-brief-template.md.template
    )
  • Research dossier (from 
    assets/research-dossier-template.md.template
    )
  • Prioritized questions and risk register captured for product-requirements skill
  • Recommendation on readiness to progress or need for further discovery
Template locations: 
.claude/skills/bmad-discovery-research/assets/*.template
  • 遵循
    REFERENCE.md
    格式的发现简报
  • 创意构思笔记（来自
    assets/brainstorm-template.md.template
    ）
  • 产品简报（来自
    assets/product-brief-template.md.template
    ）
  • 研究档案（来自
    assets/research-dossier-template.md.template
    ）
  • 为产品需求Skill整理的优先级问题和风险登记册
  • 关于是否准备好推进或需要进一步探索的建议
模板位置： 
.claude/skills/bmad-discovery-research/assets/*.template

Process

流程步骤

  1. Validate entry criteria in 
    CHECKLIST.md
    and classify project complexity.
  2. Conduct desk research across provided assets; cite sources.
  3. Frame insights into concise problem summary, goals, personas, and constraints (use templates in 
    assets/
    ).
  4. Document open questions, assumptions, and risks with recommended owners.
  5. Deliver summary plus links to created artifacts for the orchestrator and stakeholders.
Note on automation: This skill currently operates through collaborative conversation using templates. No automation scripts are required—artifacts are generated manually using Jinja2 templates from 
assets/
. See 
scripts/README.md
for future automation roadmap.
  1. 验证
    CHECKLIST.md
    中的准入标准并分类项目复杂度。
  2. 对提供的资产进行案头研究；注明来源。
  3. 将洞察整理为简洁的问题摘要、目标、用户画像和约束条件（使用
    assets/
    中的模板）。
  4. 记录未解决的问题、假设和风险，并推荐负责人。
  5. 向编排器和相关方交付摘要及生成工件的链接。
自动化说明： 此Skill目前通过使用模板的协作对话运行。无需自动化脚本——工件通过
assets/
中的Jinja2模板手动生成。请查看
scripts/README.md
了解未来自动化路线图。

Quality Gates

质量关卡

Confirm 
CHECKLIST.md
is satisfied before signaling readiness for planning. Missing data or low confidence requires escalation.
在表示准备好进入规划阶段前，需确认
CHECKLIST.md
的要求已满足。数据缺失或信心不足时需升级处理。

Error Handling

错误处理

  • If the idea remains ambiguous after initial probing, request specific clarifications rather than guessing.
  • Flag conflicting stakeholder goals and recommend alignment conversations.
  • When scope is too small (Level 0-1), suggest redirecting to lighter-weight workflows documented in 
    REFERENCE.md
    .
  • 如果经过初步询问后想法仍不明确，请求具体澄清而非猜测。
  • 标记冲突的相关方目标，并建议进行对齐对话。
  • 当范围过小（0-1级）时，建议转向
    REFERENCE.md
    中记录的轻量化工作流。