confirm-single-order-modification-intent

name: confirm-single-order-modification-intent description: Ensures the agent identifies the specific order and elicits all intended modifications for that single order when a user makes a general request for 'changes to an order', preventing unconfirmed multi-order or multi-faceted actions. metadata: benchmark: tau2_retail_cheatsheets_v2 source: /data/Research_dir/Memory/Procedual_Memory/Outputs/tau2_pairable_skill_tool.json

Layer 1: Metadata & Description

• Description: Ensures the agent identifies the specific order and elicits all intended modifications for that single order when a user makes a general request for 'changes to an order', preventing unconfirmed multi-order or multi-faceted actions.

Layer 2: Guidelines

General Guidelines

• Always clarify the specific target entity (e.g., order ID) when a general modification request is made.
• Never assume the scope or number of modifications from a vague statement.
• Avoid acting on multiple distinct orders or items when the user refers to a singular entity.
• Prioritize explicit user confirmation for all intended changes before execution.

Specific Guidelines

• If the user states 'an order', ask 'Which order are you referring to?' or 'Can you provide the order number?'
• Once an order is identified, ask 'What specific changes would you like to make to this order?'
• If historical context suggests potential changes, present them as options for the identified order and ask for confirmation, rather than executing.
• Before executing, summarize all proposed changes for the identified order and seek explicit user approval.

Layer 3: Context

• Problem Pattern: Prematurely executing multiple, distinct modifications across different orders based on a general, singular request for changes.
• State Signature: User expresses a general desire to make 'changes to an order' without specifying the order ID or the nature of the changes. Agent proceeds to execute multiple, distinct modifications across multiple orders without explicit user confirmation of the target order or the full scope of changes.
• Bypass Strategy:
  1. Identify if the user's request for 'changes to an order' is general and lacks specific order ID or modification details.
  2. If general, prompt the user to specify the exact order ID they wish to modify.
  3. Once the order is identified, prompt the user to describe all the specific changes they wish to make to that order.
  4. Confirm the complete list of intended modifications for the identified order with the user before executing any actions.