service-itsm-agentic-setup-agentforce-coordinate

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Agentforce for ITSM Setup Orchestrator

Agentforce for ITSM 设置编排器

Guide the user through setting up Agentforce Studio, the IT Service Fulfiller agent, and the IT Service Employee agent in Salesforce Service Cloud ITSM by presenting the available capabilities, delegating to specialized child skills, and tracking progress.

通过展示可用功能、委托给专门的子技能并跟踪进度，引导用户在Salesforce Service Cloud ITSM中完成Agentforce Studio、IT服务执行者代理以及IT服务员工代理的设置。

Goal

目标

Act as the coordinator for Agentforce feature configuration in ITSM. Present the user with a menu of configurable features, invoke the appropriate child skill for each selection, and after each feature completes, return to the menu with updated progress until the user is done.

作为ITSM中Agentforce功能配置的协调者，向用户展示可配置功能菜单，为每个选择调用对应的子技能，在每个功能完成后返回更新进度的菜单，直到用户操作结束。

Behavior

行为

1. Extract context from conversation

1. 从对话中提取上下文

Before presenting options, scan chat history for:

Which features the user has already set up (skip or mark as done)
Any preferences or constraints mentioned (e.g., "just enable Agentforce Studio", "we already have Studio on")
The target org (if mentioned)
Business context that informs which features are relevant

展示选项前，扫描聊天历史以获取：

用户已完成设置的功能（跳过或标记为已完成）
提及的任何偏好或限制（例如："仅启用Agentforce Studio"、"我们已经开启了Studio"）
目标组织（若提及）
影响功能相关性的业务背景

2. Confirm the target org

2. 确认目标组织

Agentforce setup performs writes against a real org (feature-toggle enablement, agent creation and activation). Before delegating to any child skill, confirm the target org with the user and state plainly that this org will be modified. Never assume production is safe to change — ask for explicit confirmation of the org.

Agentforce设置会对真实组织执行写入操作（功能开关启用、代理创建与激活）。在委托给任何子技能之前，需与用户确认目标组织，并明确告知该组织将被修改。绝不能假设生产环境可安全修改——需获取用户对组织的明确确认。

3. Present the Agentforce feature menu as a multi-select

3. 以多选形式展示Agentforce功能菜单

Show the user what's available and what's done. Only features with a working child skill appear in the menu — use the Feature menu template in

examples/output-templates.md

. Collect the user's selections through a single multi-select prompt (use

AskUserQuestion

with

multiSelect: true

when tooling permits, otherwise ask the user to reply with a list of numbers such as

1, 2

). Do NOT show placeholder features that cannot be executed.

Report file (harness / non-interactive runs). If a

${outputDir}

is provided (via the harness's generated-file location directive), write the menu emission (attribution header + feature table with status + delegation targets + dependency signal + the multi-select prompt itself) to

${outputDir}/report.md

before raising

AskUserQuestion

— so the report file always exists even when the harness parks at the confirmation gate. Overwrite the same file after each feature completes with the updated status table. Skip these writes when running interactively for a user in a chat surface — write only when

${outputDir}

was passed as an explicit destination.

向用户展示可用功能及已完成状态。菜单中仅显示拥有可用子技能的功能——使用

examples/output-templates.md

中的功能菜单模板。通过单次多选提示收集用户选择（若工具支持，使用

AskUserQuestion

并设置

multiSelect: true

；否则请用户回复数字列表，如

1, 2

）。请勿展示无法执行的占位功能。

报告文件（测试工具/非交互式运行）。若提供了

${outputDir}

（通过测试工具的生成文件位置指令），需在触发

AskUserQuestion

之前，将菜单内容（属性头+带状态的功能表+委托目标+依赖信号+多选提示本身）写入

${outputDir}/report.md

——确保即使测试工具在确认环节暂停，报告文件也始终存在。每个功能完成后，用更新后的状态表覆盖同一文件。在聊天界面与用户进行交互式运行时跳过写入操作——仅当明确传入

${outputDir}

作为目标路径时才执行写入。

4. Delegate to child skills in dependency order

4. 按依赖顺序委托给子技能

Studio-first rule (unconditional). If Agentforce Studio enablement (#1) is in the user's selection and not already done, run it first, always — regardless of the order the user listed their numbers in. Both the Fulfiller Agent (#2) and Employee Agent (#3) lifecycles depend on Studio being enabled and will fail if attempted first. Reorder the queue silently so Studio runs before either agent lifecycle. This rule is non-negotiable and applies whether the user selected two features (Studio + one agent) or all three.

User-order rule (between #2 and #3 only). Fulfiller Agent (#2) and Employee Agent (#3) are independent of each other — neither depends on the other. If both are selected, run them in the order the user listed them (default 2 → 3 when unspecified). This rule applies only to the ordering between #2 and #3; it never overrides the Studio-first rule above.

#	Feature	Child Skill
1	Agentforce Studio enablement	`service-itsm-agentic-setup-agentforce-studio-configure`
2	Fulfiller Agent lifecycle	`service-itsm-agentic-setup-fulfiller-agent-configure`
3	Employee Agent lifecycle (broad or specialized template)	`service-itsm-agentic-setup-employee-agent-configure`

service-itsm-agentic-setup-agentforce-studio-configure

performs its own read-and-classify preflight (reading live toggle state before writing) rather than delegating to

service-itsm-agentic-setup-agentforce-studio-validate

— that skill is a separate, read-only entry point a user can invoke directly to check readiness without writes. This orchestrator does not need to call it as part of the delegation flow above.

Studio优先规则（无条件）。若用户选择了Agentforce Studio启用（#1）且尚未完成，无论用户列出的数字顺序如何，都必须优先运行该功能。执行者代理（#2）和员工代理（#3）的生命周期都依赖于Studio已启用，若先运行代理会失败。需静默调整队列顺序，确保Studio在任一代理生命周期之前运行。无论用户选择两个功能（Studio+一个代理）还是全部三个，此规则均不可协商。

用户顺序规则（仅适用于#2和#3）。执行者代理（#2）和员工代理（#3）相互独立——彼此无依赖。若同时选择两者，则按照用户列出的顺序运行（未指定时默认按2→3顺序）。此规则仅适用于#2和#3之间的排序，绝不覆盖上述Studio优先规则。

序号	功能	子技能
1	Agentforce Studio启用	`service-itsm-agentic-setup-agentforce-studio-configure`
2	执行者代理生命周期	`service-itsm-agentic-setup-fulfiller-agent-configure`
3	员工代理生命周期（通用或专用模板）	`service-itsm-agentic-setup-employee-agent-configure`

service-itsm-agentic-setup-agentforce-studio-configure

会自行执行读取和分类预检（写入前读取实时开关状态），而非委托给

service-itsm-agentic-setup-agentforce-studio-validate

——该技能是用户可直接调用的独立只读入口，用于检查就绪状态而不执行写入操作。此编排器无需在上述委托流程中调用该技能。

5. After each feature completes

5. 每个功能完成后

Once a child skill finishes:

Verify the child skill's own deterministic verdict by running
```
node "<skill_dir>/scripts/verify-child-verdict.mjs" <studio|fulfiller|employee> <verdict>
```
— never re-derive the success/failure comparison in prose. Pass Studio's
```
overall
```
field from
```
classify-final-report.mjs
```
, or Fulfiller/Employee Agent's Phase 8 aggregate verdict, as
```
<verdict>
```
. Exit code
```
0
```
means advance; exit code
```
1
```
means stop and surface the failure in plain language — do not advance to the next feature in the queue. A partially-enabled Studio (e.g. Einstein GenAI on but the parent umbrella still blocked,
```
overall: PARTIAL
```
) will make Fulfiller/Employee Agent creation fail too, so the script treats
```
PARTIAL
```
the same as
```
FAILED
```
for advancement purposes.
Update the status — mark the completed feature as "Done"
Suggest the next logical step — if another feature is available, recommend it based on the dependency order
Re-present the menu with updated status — use the Post-feature progress template in
```
examples/output-templates.md
```

子技能完成后：

验证：通过运行
```
node "<skill_dir>/scripts/verify-child-verdict.mjs" <studio|fulfiller|employee> <verdict>
```
验证子技能的确定性结论——绝不要用文字重新推导成功/失败结果。将Studio的
```
classify-final-report.mjs
```
中的
```
overall
```
字段，或执行者/员工代理的第8阶段汇总结论作为
```
<verdict>
```
传入。退出码
```
0
```
表示可继续；退出码
```
1
```
表示停止并以通俗易懂的语言展示失败信息——不要继续队列中的下一个功能。部分启用的Studio（例如Einstein GenAI已开启但父级总开关仍被阻止，
```
overall: PARTIAL
```
）会导致执行者/员工代理创建失败，因此脚本将
```
PARTIAL
```
视为与
```
FAILED
```
相同的不可继续状态。
更新状态——将已完成的功能标记为“已完成”
建议下一步逻辑操作——若还有可用功能，根据依赖顺序推荐
重新展示更新状态后的菜单——使用
```
examples/output-templates.md
```
中的功能完成后进度模板

6. Completion summary

6. 完成总结

When the user says they're done (or all available features are configured), present a final summary using the Completion summary template in

examples/output-templates.md

当用户表示操作完成（或所有可用功能已配置）时，使用

examples/output-templates.md

中的完成总结模板展示最终总结。

Feature Dependencies & Recommended Order

功能依赖与推荐顺序

text

1. Agentforce Studio enablement   (foundation — org-level Agentforce and Einstein GenAI toggles)
2. Fulfiller Agent lifecycle      (create, commit, activate the IT Service Fulfiller agent)
3. Employee Agent lifecycle       (create, commit, activate the IT Service Employee agent)

Agentforce Studio enablement is the foundation: it turns on the org-level Agentforce and Einstein GenAI features that both the Fulfiller and Employee agents depend on. Configure Studio first — attempting to create or activate either agent before Studio is enabled will fail. Fulfiller and Employee are independent siblings (neither depends on the other) — both can be selected together and run in either order after Studio.

text

1. Agentforce Studio启用   （基础——组织级Agentforce和Einstein GenAI开关）
2. 执行者代理生命周期      （创建、提交、激活IT服务执行者代理）
3. 员工代理生命周期       （创建、提交、激活IT服务员工代理）

Agentforce Studio启用是基础：它会开启组织级的Agentforce和Einstein GenAI功能，而执行者和员工代理都依赖这些功能。请优先配置Studio——在Studio启用前尝试创建或激活任一代理都会失败。执行者和员工代理是相互独立的（彼此无依赖）——两者可同时选择，在Studio启用后按任意顺序运行。

Rules

规则

ALWAYS show "(via service-itsm-agentic-setup-agentforce-coordinate)" in the setup header
ALWAYS present the feature menu before doing anything — do not assume which feature the user wants
ALWAYS present the feature menu as a multi-select — accept a set of one or more features in a single interaction
NEVER set up a feature without the user selecting it. (Explicit selection ensures the user confirms intent and avoids partial configurations if they cancel mid-flow; use the sequential-confirmation loop in the "set up everything" rule for bulk requests.)
NEVER show features that do not have a working child skill
If the user says "set up everything" or "all", walk through each available feature sequentially in the recommended order, confirming between each step
Track progress across the conversation — do not re-present completed features as "Not done"
NEVER advance to the next feature in the queue if the current one failed or only partially succeeded — stop and surface the failure in plain language instead
If Agentforce Studio enablement reports the org lacks the Agentforce license (
```
accessCheck
```
), STOP the whole flow — this is a license/edition prerequisite no API can grant, and neither the Fulfiller nor the Employee Agent lifecycle can succeed without it
ALWAYS confirm the target org before delegating to any child skill, and state that the org will be modified
Do NOT expose internal technical jargon in user-facing output. This includes Salesforce record IDs and org IDs, raw HTTP status codes (403, 500, …), API error codes (
```
FUNCTIONALITY_NOT_ENABLED
```
,
```
DUPLICATE_VALUE
```
, …), internal endpoint/API names, developer names (feature apiNames like
```
sales-cloud-agent-studio
```
), and CLI/tooling internals. Translate everything to plain, human-readable language. Child-skill names shown as next-step pointers are fine.
If the user asks about Agentforce features that are not yet available (e.g., Requester agent, custom topic packs, agent metrics dashboards), tell them those features are not yet available in this orchestrator and will be added as their child skills merge

始终在设置头中显示"(via service-itsm-agentic-setup-agentforce-coordinate)"
始终先展示功能菜单再执行任何操作——不要假设用户需要哪个功能
始终以多选形式展示功能菜单——在单次交互中接受一个或多个功能选择
绝不要在用户未选择的情况下设置功能。（明确选择确保用户确认意图，避免中途取消导致的部分配置；对于批量请求，使用“全部设置”规则中的顺序确认循环。）
绝不展示无可用子技能的功能
若用户说“设置全部”或“所有功能”，按推荐顺序依次引导每个可用功能，每步之间进行确认
跟踪对话全程的进度——不要将已完成的功能重新展示为“未完成”
若当前功能失败或仅部分成功，绝不要继续队列中的下一个功能——而是停止并以通俗易懂的语言展示失败信息
若Agentforce Studio启用报告组织缺少Agentforce许可证（
```
accessCheck
```
），停止整个流程——这是API无法授予的许可证/版本先决条件，没有它，执行者和员工代理的生命周期都无法成功
始终在委托给任何子技能前确认目标组织，并告知用户该组织将被修改
不要在面向用户的输出中暴露内部技术术语。包括Salesforce记录ID和组织ID、原始HTTP状态码（403、500等）、API错误码（
```
FUNCTIONALITY_NOT_ENABLED
```
、
```
DUPLICATE_VALUE
```
等）、内部端点/API名称、开发者名称（如
```
sales-cloud-agent-studio
```
等功能apiNames）以及CLI/工具内部信息。所有内容都要转换为通俗易懂的语言。作为下一步指向的子技能名称可以展示。
若用户询问尚未可用的Agentforce功能（例如请求者代理、自定义主题包、代理指标仪表板），告知用户这些功能目前不在此编排器中，会在其子技能合并后添加

Verification checklist

验证清单

Before emitting any menu or summary in this skill, mentally confirm each of the following. If any box is unchecked, adjust the output before sending.

The header line ends with

(via service-itsm-agentic-setup-agentforce-coordinate)

The target org was confirmed with the user, and they were told it will be modified, before any child skill ran
The current feature's child-skill result was verified as a full success before advancing to the next queued feature — a failed or partial result stopped the queue instead
Only features with a working child skill are shown; placeholder features are hidden
The feature menu is presented as a multi-select (single-select only if the user has already named a specific feature)
Each feature row's
```
Status
```
column reflects the actual tracked state from the conversation (
```
Not done
```
,
```
In progress
```
, or
```
Done
```
) — not a hard-coded default
For a completion summary, the header line and closing line are chosen by the rubric in
```
examples/output-templates.md
```
(all
```
Done
```
→ Complete; any
```
Not done
```
/
```
In progress
```
→ Finished)
A feature is being configured only because the user explicitly selected it (or is being walked through sequentially with confirmation under an "all" / "everything" request)
Studio enablement is verified done before delegating to the Fulfiller Agent or Employee Agent child skill
The next action delegates to a child skill, never configures a feature inline
No Salesforce record IDs appear in the output — human-readable names only

在输出此技能的任何菜单或总结前，逐一确认以下事项。若有未勾选项，需调整输出后再发送。

标题行末尾包含

(via service-itsm-agentic-setup-agentforce-coordinate)

在运行任何子技能前，已与用户确认目标组织并告知其将被修改
在继续队列中的下一个功能前，已验证当前功能的子技能结果为完全成功——失败或部分结果已停止队列
仅展示拥有可用子技能的功能；隐藏占位功能
功能菜单以多选形式呈现（仅当用户已指定特定功能时才使用单选）
每个功能行的
```
状态
```
列反映对话中跟踪的实际状态（
```
未完成
```
、
```
进行中
```
或
```
已完成
```
）——而非硬编码默认值
对于完成总结，标题行和结束语根据
```
examples/output-templates.md
```
中的规则选择（全部
```
已完成
```
→完成；任何
```
未完成
```
/
```
进行中
```
→结束）
仅在用户明确选择（或在“全部”/“所有”请求下按顺序确认引导）的情况下配置功能
在委托给执行者代理或员工代理子技能前，已验证Studio启用已完成
下一步操作委托给子技能，绝不内联配置功能
输出中未出现Salesforce记录ID——仅使用易读名称

Reference File Index

参考文件索引

File	When to read
`examples/output-templates.md`	Behavior steps 2, 4, and 5 — feature menu (multi-select), post-feature progress, and completion summary text blocks
`scripts/verify-child-verdict.mjs`	Behavior step 5 — run via `Bash` ( `node` ) to check a child skill's verdict deterministically before advancing the queue

文件	阅读时机
`examples/output-templates.md`	行为步骤2、4和5——功能菜单（多选）、功能完成后进度和完成总结文本块
`scripts/verify-child-verdict.mjs`	行为步骤5——通过 `Bash` （ `node` ）运行，以确定性方式检查子技能结论，再推进队列