mirror of
https://github.com/forcedotcom/afv-library.git
synced 2026-07-30 11:43:26 +08:00
261abd679a
* @W-21955450@ Rename topic to subagent for Agent Script v2
Aligns with Agent Script v2 naming standards where `topic` is renamed
to `subagent` across all skill documentation and templates.
Changes:
- Agent Script templates: topic keyword → subagent keyword
- References: @topic.* → @subagent.*
- Documentation: Updated all skill references and guides
- Natural language references preserved in comments/descriptions
* Rename start_agent topic_selector to agent_router
Completes the topic → subagent terminology alignment by:
1. Renaming start_agent from topic_selector to agent_router (15 agent files)
2. Updating template topic declarations: topic {{placeholder}} → subagent {{placeholder}} (5 files)
3. Updating all @subagent.topic_selector references to @subagent.agent_router (35 occurrences)
4. Updating documentation: prose, examples, and diagrams (10 markdown files)
5. Updating comments to use agent_router terminology
Files affected:
- 22 agent template files
- 10 documentation/reference markdown files
- Template component files
The agent_router name is more descriptive of its actual function
(routing to different subagents) and completes the Agent Script v2
terminology standardization.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Rename files with "topic" to use "subagent" terminology
Completes the topic → subagent terminology alignment by renaming
files and updating all references:
**Files renamed (5):**
- multi-topic.agent → multi-subagent.agent
- template-single-topic.agent → template-single-subagent.agent
- template-multi-topic.agent → template-multi-subagent.agent
- topic-with-actions.agent → subagent-with-actions.agent
- agent-topic-map-diagrams.md → agent-subagent-map-diagrams.md
**References updated (6 docs):**
- Updated all filename references to point to new filenames
- Updated "Topic Map" → "Subagent Map" throughout documentation
- Updated "multi-topic"/"single-topic" → "multi-subagent"/"single-subagent"
Files modified:
- README.md, SKILL.md, agent-spec-template.md
- assets/agents/README.md, assets/README-legacy.md
- references/agent-design-and-spec-creation.md
This ensures consistent "subagent" terminology across filenames,
file content, and all documentation references.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Complete topic-to-subagent terminology update across skills
Comprehensive update replacing "topic" with "subagent" terminology throughout
the developing-agentforce and testing-agentforce skills to align with Agent
Script's `subagent` block naming.
Key changes:
- "Topic Selector" → "Subagent Router" in all agent templates and docs
- "Topic/action" → "Subagent/action" in documentation
- "Topic map" → "Subagent map" in diagram references
- Updated all architecture documentation to use "subagent" terminology
- Updated 19 .agent template files with new labels and comments
- Updated 8 reference documentation files with consistent terminology
API contract preservation:
- Test spec YAML files preserve "topic" terminology to match Testing Center API
- Added clarifying comments explaining topic/subagent equivalence in YAML files
- Field names like `expectedTopic` unchanged (Salesforce API requirement)
Preserved terms:
- "off-topic" (standard phrase for out-of-scope)
- "expectedTopic" field (Testing Center API)
- "platform topics" (Salesforce guardrail features)
32 files changed, 379 insertions(+), 366 deletions(-)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Complete comprehensive topic-to-subagent terminology update
Thorough update replacing all remaining "topic" references with "subagent"
terminology across developing-agentforce, testing-agentforce, and
observing-agentforce skills to fully align with Agent Script's `subagent`
block naming.
Key changes:
- Agent Script syntax: @topic.<name> → @subagent.<name>
- Agent Script syntax: topic.actions → subagent.actions
- Shell script patterns: ^topic → ^subagent
- Documentation: "topic instructions" → "subagent instructions"
- observing-agentforce skill: Updated all agent architecture references
- Template files: Updated all inline comments and descriptions
- Variable names in scripts: TOPIC → SUBAGENT
Specific updates:
- 45 files changed, 294 insertions, 294 deletions
- Updated all Agent Script code examples to use @subagent syntax
- Updated observing-agentforce issue classification guide
- Updated shell script patterns in diagnostic tools
- Updated Apex comments to clarify topic field maps to subagents
Preserved (as required):
- "off-topic" and "off_topic" (standard out-of-scope phrase)
- Testing Center API fields: expectedTopic, topic: in YAML
- API response fields: .topic, generatedData.topic, topic_assertion
- STDM field names: ssot__TopicApiName__c (with clarifying docs)
- Template placeholders in test specs (API values)
- "Topic hash drift" (API field behavior)
- "Email topic/purpose" (means email subject)
- Explanatory comments about API field mapping
All Agent Script syntax and documentation now consistently uses "subagent"
while preserving backward compatibility with platform API field names.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* a few more topic -> subagent replacements
---------
Co-authored-by: Steve Hetzel <shetzel@salesforce.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
82 lines
3.1 KiB
Plaintext
82 lines
3.1 KiB
Plaintext
# Single-Subagent Template
|
|
# Copy this file to your AiAuthoringBundle directory and rename it to match
|
|
# your agent's developer_name. Replace all placeholder values with real ones.
|
|
|
|
system:
|
|
instructions: "You are a helpful assistant. Describe the agent's persona and purpose here."
|
|
messages:
|
|
welcome: "Hello! How can I help you today?"
|
|
error: "Sorry, it looks like something has gone wrong."
|
|
|
|
config:
|
|
developer_name: "Agent_API_Name"
|
|
agent_label: "Agent Display Name"
|
|
description: "Description of the agent's purpose"
|
|
# agent_type: "AgentforceServiceAgent" for customer-facing (requires default_agent_user)
|
|
# "AgentforceEmployeeAgent" for internal (remove default_agent_user line)
|
|
agent_type: "AgentforceServiceAgent"
|
|
default_agent_user: "username@identifier.org"
|
|
|
|
language:
|
|
default_locale: "en_US"
|
|
additional_locales: ""
|
|
all_additional_locales: False
|
|
|
|
start_agent agent_router:
|
|
description: "Welcome the user and determine the appropriate subagent based on user input"
|
|
reasoning:
|
|
actions:
|
|
go_to_main: @utils.transition to @subagent.main
|
|
go_to_escalation: @utils.transition to @subagent.escalation
|
|
go_to_off_topic: @utils.transition to @subagent.off_topic
|
|
|
|
subagent main:
|
|
label: "Main Subagent"
|
|
description: "Describe what this subagent handles. The Atlas Reasoning Engine matches user utterances against this description."
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| Replace this with instructions for how the agent should handle requests in this subagent.
|
|
Reference actions with the syntax shown below.
|
|
|
|
actions:
|
|
do_action: @actions.do_action
|
|
with input_param = ...
|
|
|
|
actions:
|
|
do_action:
|
|
description: "Describe what this action does"
|
|
label: "Action Display Name"
|
|
target: "apex://ClassName"
|
|
inputs:
|
|
input_param: string
|
|
description: "Describe this parameter"
|
|
label: "Parameter Display Name"
|
|
is_required: True
|
|
outputs:
|
|
output_field: string
|
|
label: "Output Display Name"
|
|
description: "Describe this output"
|
|
is_displayable: True
|
|
filter_from_agent: False
|
|
|
|
subagent escalation:
|
|
label: "Escalation"
|
|
description: "Handles requests from users who want to transfer or escalate their conversation to a live human agent."
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| If a user explicitly asks to transfer to a live agent, escalate the conversation.
|
|
actions:
|
|
escalate_to_human: @utils.escalate
|
|
description: "Escalate to a human agent."
|
|
|
|
subagent off_topic:
|
|
label: "Off Topic"
|
|
description: "Redirect conversation to relevant subagents when user request goes off-topic"
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| The user request is off-topic. Do not answer general knowledge questions.
|
|
Redirect the conversation by asking how you can help with the subagents this agent supports.
|