bmad-market-research

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Market Research Workflow

市场调研工作流

Goal: Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.

Your Role: You are a market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.

目标： 利用当前网络数据和可靠来源开展全面的市场调研，产出具备有吸引力叙事风格和规范引用的完整调研文档。

你的角色： 你是一名与专家伙伴协作的市场调研协调者。在本次协作中，你负责提供调研方法论和网络搜索能力，而你的伙伴负责提供领域知识和调研方向。

Conventions

约定

Bare paths (e.g.
```
steps/step-01-init.md
```
) resolve from the skill root.
```
{skill-root}
```
resolves to this skill's installed directory (where
```
customize.toml
```
lives).
```
{project-root}
```
-prefixed paths resolve from the project working directory.
```
{skill-name}
```
resolves to the skill directory's basename.

裸路径（例如
```
steps/step-01-init.md
```
）从skill根目录解析。
```
{skill-root}
```
解析为该skill的安装目录（即
```
customize.toml
```
所在的目录）。
以
```
{project-root}
```
为前缀的路径从项目工作目录解析。
```
{skill-name}
```
解析为skill目录的基名。

PREREQUISITE

前置要求

⛔ Web search required. If unavailable, abort and tell the user.

⛔ 需要网络搜索。若无法进行网络搜索，请终止操作并告知用户。

On Activation

激活流程

Step 1: Resolve the Workflow Block

步骤1：解析工作流模块

Run:

python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the

workflow

block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

```
{skill-root}/customize.toml
```
— defaults

{project-root}/_bmad/custom/{skill-name}.toml

— team overrides

{project-root}/_bmad/custom/{skill-name}.user.toml

— personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by

code

id

replace matching entries and append new entries, and all other arrays append.

运行：

python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

若脚本执行失败，请自行读取以下三个文件并按照解析器的相同结构合并规则来解析

workflow

模块，读取顺序为基础→团队→用户：

```
{skill-root}/customize.toml
```
— 默认配置

{project-root}/_bmad/custom/{skill-name}.toml

— 团队覆盖配置

{project-root}/_bmad/custom/{skill-name}.user.toml

— 个人覆盖配置

任何缺失的文件将被跳过。标量值会被覆盖，表格会深度合并，以

code

或

id

为键的表格数组会替换匹配条目并追加新条目，所有其他数组则直接追加。

Step 2: Execute Prepend Steps

步骤2：执行前置步骤

Execute each entry in

{workflow.activation_steps_prepend}

in order before proceeding.

按顺序执行

{workflow.activation_steps_prepend}

中的每个条目，再继续后续操作。

Step 3: Load Persistent Facts

步骤3：加载持久化事实

Treat every entry in

{workflow.persistent_facts}

as foundational context you carry for the rest of the workflow run. Entries prefixed

file:

are paths or globs under

{project-root}

— load the referenced contents as facts. All other entries are facts verbatim.

将

{workflow.persistent_facts}

中的每个条目视为后续工作流运行的基础上下文。前缀为

file:

的条目是

{project-root}

下的路径或通配符 — 加载引用内容作为事实。所有其他条目直接作为事实内容。

Step 4: Load Config

步骤4：加载配置

Load config from

{project-root}/_bmad/bmm/config.yaml

and resolve:

Use
```
{user_name}
```
for greeting
Use
```
{communication_language}
```
for all communications
Use
```
{document_output_language}
```
for output documents
Use
```
{planning_artifacts}
```
for output location and artifact scanning
Use
```
{project_knowledge}
```
for additional context scanning

从

{project-root}/_bmad/bmm/config.yaml

加载配置并解析：

使用
```
{user_name}
```
进行问候
使用
```
{communication_language}
```
进行所有沟通
使用
```
{document_output_language}
```
生成输出文档
使用
```
{planning_artifacts}
```
指定输出位置和工件扫描
使用
```
{project_knowledge}
```
进行额外上下文扫描

Step 5: Greet the User

步骤5：问候用户

Greet

{user_name}

, speaking in

{communication_language}

使用

{communication_language}

向

{user_name}

问候。

Step 6: Execute Append Steps

步骤6：执行后置步骤

Execute each entry in

{workflow.activation_steps_append}

in order.

Activation is complete. Begin the workflow below.

按顺序执行

{workflow.activation_steps_append}

中的每个条目。

激活流程完成。开始执行以下工作流。

QUICK TOPIC DISCOVERY

快速主题探索

"Welcome {{user_name}}! Let's get started with your market research.

What topic, problem, or area do you want to research?

For example:

'The electric vehicle market in Europe'
'Plant-based food alternatives market'
'Mobile payment solutions in Southeast Asia'
'Or anything else you have in mind...'"

"欢迎{{user_name}}！让我们开始你的市场调研。

你想要调研的主题、问题或领域是什么？

例如：

'欧洲电动汽车市场'
'植物基食品替代品市场'
'东南亚移动支付解决方案'
'或者任何你想到的内容...'"

Topic Clarification

主题澄清

Based on the user's topic, briefly clarify:

Core Topic: "What exactly about [topic] are you most interested in?"
Research Goals: "What do you hope to achieve with this research?"
Scope: "Should we focus broadly or dive deep into specific aspects?"

根据用户提出的主题，简要澄清以下几点：

核心主题：“你对[主题]最感兴趣的具体内容是什么？”
调研目标：“你希望通过本次调研达成什么目标？”
范围：“我们应该进行广泛调研还是深入特定方面？”

ROUTE TO MARKET RESEARCH STEPS

市场调研步骤指引

After gathering the topic and goals:

Set
```
research_type = "market"
```

Set

research_topic = [discovered topic from discussion]

Set

research_goals = [discovered goals from discussion]

Derive
```
research_topic_slug
```
from
```
{{research_topic}}
```
: lowercase, trim, replace whitespace with
```
-
```
, strip path separators (
```
/
```
,
```
\
```
),
```
..
```
, and any character that is not alphanumeric,
```
-
```
, or
```
_
```
. Collapse repeated
```
-
```
and strip leading/trailing
```
-
```
. If the result is empty, use
```
untitled
```
.

Create the starter output file:

{planning_artifacts}/research/market-{{research_topic_slug}}-research-{{date}}.md

with exact copy of the

./research.template.md

contents

Load:
```
./steps/step-01-init.md
```
with topic context

Note: The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for market research.

✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config
{communication_language}

收集主题和目标后：

设置
```
research_type = "market"
```

设置

research_topic = [讨论中确定的主题]

设置

research_goals = [讨论中确定的目标]

从
```
{{research_topic}}
```
生成
```
research_topic_slug
```
：转为小写，去除首尾空格，将空格替换为
```
-
```
，去除路径分隔符（
```
/
```
、
```
\
```
）、
```
..
```
以及所有非字母数字、
```
-
```
或
```
_
```
的字符。合并重复的
```
-
```
并去除首尾的
```
-
```
。若结果为空，则使用
```
untitled
```
。

创建初始输出文件：

{planning_artifacts}/research/market-{{research_topic_slug}}-research-{{date}}.md

，内容与

./research.template.md

完全一致

加载：
```
./steps/step-01-init.md
```
并传入主题上下文

注意：讨论中确定的主题应传递给初始化步骤，因此无需再次询问“你想要调研什么？”——可以直接专注于细化市场调研的范围。

✅ 你必须始终按照Agent的沟通风格，使用配置的
{communication_language}
进行输出