clarify-general-adjustment-intent

name: clarify-general-adjustment-intent description: Prevents the agent from prematurely assuming a specific action (e.g., cancellation) when a user expresses a general desire for 'adjustments' or 'changes'. 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 prematurely assuming a specific action (e.g., cancellation) when a user expresses a general desire for 'adjustments' or 'changes'.

Layer 2: Guidelines

General Guidelines

• Do not assume the specific action (e.g., cancellation, modification, return) when a user expresses a general need for 'adjustments' or 'changes'.
• Always clarify the exact type of action the user intends before proceeding.
• Treat general problem statements as an opportunity to gather specific intent.
• Avoid reporting an action as completed or in progress until the user has explicitly confirmed the specific action.

Specific Guidelines

• When a user states a general desire for 'adjustments,' ask 'What kind of adjustment are you looking to make?'
• If multiple entities are implied, ask 'Which specific order or item are you referring to for this adjustment?'
• Before executing any action, explicitly state the understood action and item(s) for user confirmation.
• If the user mentions 'a mistake,' prompt them to describe the nature of the mistake and their desired resolution.

Layer 3: Context

• Problem Pattern: Prematurely assuming the specific type of modification or action when a general request for change is made
• State Signature: User expresses a general desire for adjustment or correction without specifying the exact action, and the agent proceeds with or reports a specific assumed action
• Bypass Strategy:
  1. Acknowledge the user's general request for adjustment.
  2. Prompt the user to specify the exact action they wish to take.
  3. Confirm the specific entities (e.g., orders, items) involved in the requested action.
  4. Obtain explicit user confirmation of the specific action before execution or reporting.