Update to Appy Coupons - deals+discounts

{
  "description": "Build a conservative coupon stacking and fallback plan when the user asks whether supplied coupons can combine or which order to try at checkout. Use explicit merchant terms and cart facts, distinguish confirmed compatibility from unknown compatibility, and present the attempt order with the `coupons` app tool. Never claim an untested stack will work.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 222
    }
  ],
  "name": "coupon-stacking-plan",
  "skill_md_contents": "---\nname: coupon-stacking-plan\ndescription: Build a conservative coupon stacking and fallback plan when the user asks whether supplied coupons can combine or which order to try at checkout. Use explicit merchant terms and cart facts, distinguish confirmed compatibility from unknown compatibility, and present the attempt order with the `coupons` app tool. Never claim an untested stack will work.\n---\n\n# Coupon stacking plan\n\nConvert supplied coupon terms into an evidence-based checkout attempt order.\n\n## Inputs\n\nIdentify the candidate coupons, merchant, market, checkout channel, relevant cart items and total, user eligibility, and savings goal. Ask for a missing cart fact only when it changes eligibility or ranking.\n\n## Workflow\n\n1. Extract stacking, minimum-spend, product, membership, channel, expiry, and exclusion terms from the information already supplied. Do not substitute general retailer assumptions for missing policy.\n2. Classify each relationship as confirmed combinable, confirmed incompatible, or unknown. Reserve confirmed combinable for terms that explicitly allow the combination.\n3. Remove offers known to be expired or ineligible. Estimate savings only from explicit discount mechanics and available cart facts; label estimates and omit taxes, shipping, or category assumptions that are not supplied.\n4. Build a primary plan from confirmed-compatible offers only. When no combination is confirmed, choose the strongest eligible single offer as the first attempt and keep other offers as fallbacks. Put unknown combinations in a separately labeled checkout test, never in the confirmed plan.\n5. Order coupons in the sequence the user should attempt them. Preserve each offer's facts and append a short stacking status and rationale to `notes`.\n6. Call `coupons` when the plan contains at least one candidate, using the planned attempt order and a concise `reason`.\n7. Explain the primary plan, fallbacks, unknown tests, and the evidence behind each classification. Tell the user to review the checkout total before placing the order.\n\n## Boundaries\n\n- The app can display and copy coupon codes, but it cannot apply codes, inspect a checkout, redeem an offer, or observe whether a merchant accepted a stack.\n- Do not call an unknown combination compatible merely because neither coupon says otherwise.\n- Do not state a final savings amount when required cart details are missing.\n- Do not call `coupons` with an empty plan.\n\n## Output\n\nReturn the ordered coupon widget plus a concise primary plan, fallback sequence, and uncertainty notes.\n"
}