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>
90 lines
4.6 KiB
Plaintext
90 lines
4.6 KiB
Plaintext
# Subagent Delegation vs Transition Pattern
|
|
# Understanding the difference between delegation and permanent handoffs
|
|
#
|
|
# ★ KEY CONCEPTS:
|
|
#
|
|
# DELEGATION (@subagent.* syntax):
|
|
# - Syntax: action_name: @subagent.subagent_name
|
|
# - Control CAN return to the calling subagent
|
|
# - Use for: consulting specialists, sub-tasks, getting help
|
|
#
|
|
# TRANSITION (@utils.transition syntax):
|
|
# - Syntax: action_name: @utils.transition to @subagent.subagent_name
|
|
# - PERMANENT handoff - control does NOT return
|
|
# - Use for: menu navigation, workflow stages, permanent routing
|
|
#
|
|
# ★ When To Use Each:
|
|
# DELEGATION: "Consult an expert then continue here"
|
|
# TRANSITION: "Go to this subagent and stay there"
|
|
#
|
|
# ★ Implementation Note:
|
|
# If delegation syntax doesn't work in your deployment method,
|
|
# use the bidirectional-routing.agent pattern which manually
|
|
# tracks return context via variables.
|
|
#
|
|
# This is a PARTIAL template - integrate into a complete agent file
|
|
|
|
# ═══════════════════════════════════════════════════════════════
|
|
# PATTERN 1: Subagent Delegation (can return)
|
|
# ═══════════════════════════════════════════════════════════════
|
|
|
|
# Delegation syntax in reasoning.actions:
|
|
#
|
|
# reasoning:
|
|
# actions:
|
|
# # Delegation - specialist CAN return control to this subagent
|
|
# consult_expert: @subagent.specialist_subagent
|
|
# description: "Consult specialist for complex questions"
|
|
# available when @variables.needs_expert_help == True
|
|
#
|
|
# The specialist subagent processes the request and control returns
|
|
# to the original subagent when done.
|
|
|
|
# ═══════════════════════════════════════════════════════════════
|
|
# PATTERN 2: Transition (permanent handoff)
|
|
# ═══════════════════════════════════════════════════════════════
|
|
|
|
# Transition syntax in reasoning.actions:
|
|
#
|
|
# reasoning:
|
|
# actions:
|
|
# # Transition - permanent move to orders subagent
|
|
# go_orders: @utils.transition to @subagent.orders
|
|
#
|
|
# Control moves to orders subagent and STAYS there.
|
|
# User continues in that subagent until another transition occurs.
|
|
|
|
# ═══════════════════════════════════════════════════════════════
|
|
# PATTERN 3: Manual Bidirectional (fallback pattern)
|
|
# ═══════════════════════════════════════════════════════════════
|
|
|
|
# If delegation doesn't work, use variables to track return:
|
|
# See: bidirectional-routing.agent for full implementation
|
|
|
|
variables:
|
|
return_subagent: mutable string = ""
|
|
description: "Subagent to return to after specialist"
|
|
specialist_result: mutable string = ""
|
|
description: "Result from specialist consultation"
|
|
|
|
# Before going to specialist, store return address:
|
|
# set @variables.return_subagent = "main_hub"
|
|
# go_specialist: @utils.transition to @subagent.specialist
|
|
|
|
# In specialist, transition back when done:
|
|
# return_home: @utils.transition to @subagent.main_hub
|
|
|
|
# ═══════════════════════════════════════════════════════════════
|
|
# COMPARISON TABLE
|
|
# ═══════════════════════════════════════════════════════════════
|
|
#
|
|
# | Feature | Delegation | Transition |
|
|
# |----------------------|-------------------|-------------------------|
|
|
# | Syntax | @subagent.name | @utils.transition to |
|
|
# | Returns to caller? | YES | NO |
|
|
# | Use in actions: | YES | YES |
|
|
# | Use in lifecycle: | NO | YES (bare syntax) |
|
|
# | Best for | Consult & return | Menu/workflow routing |
|
|
#
|
|
# ═══════════════════════════════════════════════════════════════
|