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