mirror of
https://github.com/forcedotcom/afv-library.git
synced 2026-07-30 19:50:42 +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>
106 lines
3.1 KiB
Plaintext
106 lines
3.1 KiB
Plaintext
# Multi-Subagent Agent Template
|
|
# An agent with multiple conversation subagents (hub-and-spoke pattern)
|
|
# Users are routed to specialized subagents based on their needs
|
|
#
|
|
# Usage: Replace {{placeholders}} with your values
|
|
# Required: agent_name, default_agent_user, agent_label, description
|
|
# Required: At least 2 subagents with label and description
|
|
|
|
system:
|
|
instructions: "{{SystemInstructions}}"
|
|
messages:
|
|
welcome: "{{WelcomeMessage}}"
|
|
error: "I'm sorry, I encountered an issue. Please try again."
|
|
|
|
config:
|
|
agent_name: "{{AgentApiName}}"
|
|
default_agent_user: "{{AgentUser}}"
|
|
agent_label: "{{AgentLabel}}"
|
|
description: "{{AgentDescription}}"
|
|
|
|
variables:
|
|
EndUserId: linked string
|
|
source: @MessagingSession.MessagingEndUserId
|
|
description: "Messaging End User ID"
|
|
RoutableId: linked string
|
|
source: @MessagingSession.Id
|
|
description: "Messaging Session ID"
|
|
ContactId: linked string
|
|
source: @MessagingEndUser.ContactId
|
|
description: "Contact ID"
|
|
user_intent: mutable string
|
|
description: "What the user is trying to accomplish"
|
|
|
|
language:
|
|
default_locale: "en_US"
|
|
additional_locales: ""
|
|
all_additional_locales: False
|
|
|
|
start_agent agent_router:
|
|
label: "Subagent Router"
|
|
description: "Routes users to the appropriate subagent based on their needs"
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| Determine what the user needs help with.
|
|
| Route them to the most appropriate subagent.
|
|
| If unclear, ask clarifying questions.
|
|
actions:
|
|
go_to_subagent_one: @utils.transition to @subagent.{{subagent_one_name}}
|
|
go_to_subagent_two: @utils.transition to @subagent.{{subagent_two_name}}
|
|
go_to_subagent_three: @utils.transition to @subagent.{{subagent_three_name}}
|
|
go_to_farewell: @utils.transition to @subagent.farewell
|
|
go_to_escalation: @utils.transition to @subagent.escalation
|
|
|
|
subagent {{subagent_one_name}}:
|
|
label: "{{SubagentOneLabel}}"
|
|
description: "{{SubagentOneDescription}}"
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| {{SubagentOneInstructions}}
|
|
actions:
|
|
back_to_menu: @utils.transition to @subagent.agent_router
|
|
|
|
subagent {{subagent_two_name}}:
|
|
label: "{{SubagentTwoLabel}}"
|
|
description: "{{SubagentTwoDescription}}"
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| {{SubagentTwoInstructions}}
|
|
actions:
|
|
back_to_menu: @utils.transition to @subagent.agent_router
|
|
|
|
subagent {{subagent_three_name}}:
|
|
label: "{{SubagentThreeLabel}}"
|
|
description: "{{SubagentThreeDescription}}"
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| {{SubagentThreeInstructions}}
|
|
actions:
|
|
back_to_menu: @utils.transition to @subagent.agent_router
|
|
|
|
subagent farewell:
|
|
label: "Farewell"
|
|
description: "Ends the conversation gracefully"
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| Thank the user for reaching out.
|
|
| Wish them a great day.
|
|
| Let them know they can return anytime.
|
|
|
|
subagent escalation:
|
|
label: "Escalation"
|
|
description: "Handles requests to transfer to a live human agent"
|
|
|
|
reasoning:
|
|
instructions: ->
|
|
| If the user explicitly asks to speak with a human, escalate.
|
|
| Acknowledge the request and transfer gracefully.
|
|
actions:
|
|
escalate_to_human: @utils.escalate
|
|
description: "Escalate to a human agent"
|