confirm-unchanged-replacement-attributes

name: confirm-unchanged-replacement-attributes description: Prevents the agent from assuming or changing unstated attributes (e.g., color, material) of a replacement item when a user requests a modification to only one specific attribute (e.g., size), without confirming user preference for those unstated attributes. metadata: benchmark: tau2_retail_cheatsheets_v2 source: /data/Research_dir/Memory/Procedual_Memory/Outputs/tau2_pairable_skill_tool.json

Layer 1: Metadata & Description

• Description: Prevents the agent from assuming or changing unstated attributes (e.g., color, material) of a replacement item when a user requests a modification to only one specific attribute (e.g., size), without confirming user preference for those unstated attributes.

Layer 2: Guidelines

General Guidelines

• Do not assume preferences for attributes of a replacement item that were not explicitly mentioned by the user.
• Explicitly confirm or elicit preferences for all relevant attributes of a replacement item, even if only one attribute was requested for change.
• Prioritize retaining the original item's unstated attributes as the default unless the user specifies otherwise.
• Avoid proposing a replacement item with unconfirmed attribute changes (e.g., a different color) without user input.

Specific Guidelines

• When a user requests a size change for an item, explicitly ask if they want to keep the original color, material, and style, or if they have new preferences.
• If the original item's attributes are known, present them as the default option for the replacement and ask for confirmation (e.g., 'Do you want the same Red color and Cotton material?').
• If the user does not specify other attributes, do not introduce new ones (e.g., a different color) without asking.
• Before finalizing an exchange, confirm the complete description of the new item, including all attributes, to ensure it matches user preferences.

Layer 3: Context

• Problem Pattern: Assuming unstated attributes for a replacement item.
• State Signature: User requests a modification to a specific attribute of an item, but the agent proposes a replacement item with different or unconfirmed values for other attributes without explicit user input or confirmation.
• Bypass Strategy:
  1. Identify the item to be exchanged and the explicitly requested attribute modification.
  2. Identify all other relevant attributes of the original item.
  3. Before proposing a specific replacement, explicitly confirm with the user if they wish to retain the original values for the unstated attributes, or if they have new preferences.
  4. Elicit specific preferences for any unstated attributes the user wishes to change.
  5. Propose a replacement item that matches the explicitly requested modification and the confirmed/elicited preferences for all other attributes.