mirror of
https://github.com/forcedotcom/afv-library.git
synced 2026-08-01 04:16:17 +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>
105 lines
3.9 KiB
Plaintext
105 lines
3.9 KiB
Plaintext
# Hub-and-Spoke Architecture Template
|
|
# ====================================
|
|
#
|
|
# This template demonstrates the Hub-and-Spoke pattern where a central
|
|
# agent_router (hub) routes conversations to specialized subagents (spokes).
|
|
#
|
|
# Pattern: Multi-purpose agents handling distinct request types
|
|
# Use when: Users may have different intents (orders, support, returns)
|
|
|
|
system:
|
|
messages:
|
|
welcome: "Welcome! I can help with orders, returns, or general support."
|
|
error: "I apologize, something went wrong. Let me try again."
|
|
instructions: "You are a customer service agent for an e-commerce company."
|
|
|
|
config:
|
|
agent_name: "HubAndSpokeAgent"
|
|
agent_label: "Customer Service Agent"
|
|
description: "Multi-purpose agent with hub-and-spoke architecture"
|
|
default_agent_user: "agent@yourorg.com" # REQUIRED: Change to valid Einstein Agent User
|
|
|
|
variables:
|
|
customer_id: linked string
|
|
source: @session.customerId
|
|
description: "Customer ID from session"
|
|
order_id: mutable string = ""
|
|
description: "Current order being discussed"
|
|
issue_resolved: mutable boolean = False
|
|
description: "Whether the issue has been resolved"
|
|
|
|
# ============================================================
|
|
# HUB: Central Router
|
|
# ============================================================
|
|
|
|
start_agent agent_router:
|
|
description: "Route to appropriate subagent based on user intent"
|
|
reasoning:
|
|
instructions: |
|
|
Determine what the customer needs and route accordingly:
|
|
- Order questions → orders subagent
|
|
- Return/refund requests → returns subagent
|
|
- General questions → support subagent
|
|
actions:
|
|
check_order: @utils.transition to @subagent.orders
|
|
description: "Customer wants to check order status"
|
|
process_return: @utils.transition to @subagent.returns
|
|
description: "Customer wants to return or refund"
|
|
general_help: @utils.transition to @subagent.support
|
|
description: "General support questions"
|
|
|
|
# ============================================================
|
|
# SPOKE: Orders Subagent
|
|
# ============================================================
|
|
|
|
subagent orders:
|
|
description: "Handle order status and tracking inquiries"
|
|
reasoning:
|
|
instructions: ->
|
|
| Help the customer with their order inquiry.
|
|
|
|
if @variables.order_id != "":
|
|
| Current order: {!@variables.order_id}
|
|
|
|
actions:
|
|
lookup_order: @actions.get_order_status
|
|
description: "Look up order details"
|
|
with order_id = @variables.order_id
|
|
back_to_hub: @utils.transition to @subagent.agent_router
|
|
description: "Return to main menu"
|
|
|
|
# ============================================================
|
|
# SPOKE: Returns Subagent
|
|
# ============================================================
|
|
|
|
subagent returns:
|
|
description: "Handle return and refund requests"
|
|
reasoning:
|
|
instructions: ->
|
|
| Help the customer with their return or refund request.
|
|
| Verify the order details before processing.
|
|
|
|
actions:
|
|
start_return: @actions.initiate_return
|
|
description: "Start a return process"
|
|
process_refund: @actions.process_refund
|
|
description: "Process a refund"
|
|
back_to_hub: @utils.transition to @subagent.agent_router
|
|
description: "Return to main menu"
|
|
|
|
# ============================================================
|
|
# SPOKE: Support Subagent
|
|
# ============================================================
|
|
|
|
subagent support:
|
|
description: "Handle general support questions"
|
|
reasoning:
|
|
instructions: |
|
|
Help the customer with general questions.
|
|
If the question requires specialized help, route appropriately.
|
|
actions:
|
|
escalate: @utils.escalate
|
|
description: "Transfer to human agent"
|
|
back_to_hub: @utils.transition to @subagent.agent_router
|
|
description: "Return to main menu"
|