afv-library/skills/developing-agentforce/assets/deterministic-routing.agent

167 lines
7.1 KiB
Plaintext
Raw Normal View History

# Deterministic Routing Template (Zero-Hallucination Pattern)
# ============================================================
#
# This template demonstrates the zero-hallucination intent classification
# pattern using action output flags to control LLM behavior.
#
# Pattern: Classify intent deterministically, route without hallucination
# Use when: Critical routing decisions that must not be influenced by LLM creativity
#
# KEY PATTERN:
# In Agentforce Assets, set action outputs with:
# - is_displayable: False (LLM cannot show this to user)
# - is_used_by_planner: True (LLM can use for routing)
#
# This ensures the LLM routes based on classification but cannot
# generate hallucinated responses based on the classification data.
system:
messages:
welcome: "Hello! How can I help you today?"
error: "I apologize, something went wrong. Let me try again."
instructions: "You are a customer service agent. Route users to the correct department based on their intent."
config:
agent_name: "DeterministicRoutingAgent"
agent_label: "Smart Router Agent"
description: "Agent demonstrating zero-hallucination intent routing pattern"
default_agent_user: "agent@yourorg.com" # REQUIRED: Change to valid Einstein Agent User
variables:
# Intent classification (populated by action with is_displayable: False)
classified_intent: mutable string = ""
description: "Classification result - hidden from user responses"
confidence_score: mutable number = 0
description: "Classification confidence (0-100)"
# Routing state
needs_classification: mutable boolean = True
description: "Whether user intent needs classification"
low_confidence_warning: mutable boolean = False
description: "Flag for low confidence routing"
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
start_agent agent_router:
description: "Classify intent and route deterministically"
reasoning:
instructions: ->
# ====================================================
# DETERMINISTIC ROUTING (based on classified_intent)
# ====================================================
# Route ONLY when classification is complete
if @variables.needs_classification == False:
# HIGH-CONFIDENCE ROUTING
if @variables.confidence_score >= 80:
if @variables.classified_intent == "billing":
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
transition to @subagent.billing
if @variables.classified_intent == "technical_support":
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
transition to @subagent.technical_support
if @variables.classified_intent == "sales":
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
transition to @subagent.sales
if @variables.classified_intent == "returns":
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
transition to @subagent.returns
# LOW-CONFIDENCE: Confirm with user
if @variables.confidence_score < 80:
set @variables.low_confidence_warning = True
| I want to make sure I route you correctly.
| It sounds like you need help with **{!@variables.classified_intent}**.
| Is that correct?
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
# INITIAL STATE: Ask for help subject
if @variables.needs_classification == True:
| I can help with billing, technical support, sales, or returns.
| What do you need help with today?
actions:
# CRITICAL: This action's outputs must be configured in Agentforce Assets:
# - classified_intent: is_displayable=False, is_used_by_planner=True
# - confidence_score: is_displayable=False, is_used_by_planner=True
#
# This ensures LLM cannot hallucinate based on classification data
classify_intent: @actions.Classify_User_Intent
description: "Determine what the user needs help with"
with user_message = ... # LLM extracts from conversation
set @variables.classified_intent = @outputs.intent
set @variables.confidence_score = @outputs.confidence
set @variables.needs_classification = False
# Manual routing for low-confidence cases
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
go_billing: @utils.transition to @subagent.billing
description: "Yes, I need billing help"
available when @variables.low_confidence_warning == True and @variables.classified_intent == "billing"
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
go_support: @utils.transition to @subagent.technical_support
description: "Yes, I need technical support"
available when @variables.low_confidence_warning == True and @variables.classified_intent == "technical_support"
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
go_sales: @utils.transition to @subagent.sales
description: "Yes, I need sales help"
available when @variables.low_confidence_warning == True and @variables.classified_intent == "sales"
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
go_returns: @utils.transition to @subagent.returns
description: "Yes, I need returns help"
available when @variables.low_confidence_warning == True and @variables.classified_intent == "returns"
# Reclassify if user said "no"
reclassify: @utils.setVariables
description: "That's not what I need - let me clarify"
available when @variables.low_confidence_warning == True
with needs_classification = True
with classified_intent = ""
with confidence_score = 0
with low_confidence_warning = False
# ============================================================
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
# ROUTED SUBAGENTS
# ============================================================
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
subagent billing:
description: "Handle billing inquiries"
reasoning:
instructions: |
Help the customer with their billing question.
You can view invoices, explain charges, or process payments.
actions:
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
back: @utils.transition to @subagent.agent_router
description: "Return to main menu"
escalate_now: @utils.escalate
description: "Transfer to billing specialist"
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
subagent technical_support:
description: "Handle technical support issues"
reasoning:
instructions: |
Help the customer with their technical issue.
Troubleshoot problems and provide solutions.
actions:
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
back: @utils.transition to @subagent.agent_router
description: "Return to main menu"
escalate_now: @utils.escalate
description: "Transfer to technical specialist"
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
subagent sales:
description: "Handle sales inquiries"
reasoning:
instructions: |
Help the customer with sales questions.
Provide product information and pricing.
actions:
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
back: @utils.transition to @subagent.agent_router
description: "Return to main menu"
escalate_now: @utils.escalate
description: "Transfer to sales representative"
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
subagent returns:
description: "Handle return requests"
reasoning:
instructions: |
Help the customer with their return request.
Check eligibility and process returns.
actions:
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193) * @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>
2026-04-28 02:42:18 +08:00
back: @utils.transition to @subagent.agent_router
description: "Return to main menu"
escalate_now: @utils.escalate
description: "Transfer to returns specialist"