What problem does it solve? Refunds move real money and are irreversible, so handling them as a single button press causes errors, double refunds, and orphaned approvals that permanently block later payment corrections. This Skill enforces a safe three-stage flow (request → approve → execute) with human confirmation at every gate for the rocky-regi restaurant POS. ## Core Features & Use Cases - Three-stage gated refunds: Runs request_refund, approve_refund, and execute_refund strictly in order, one transaction at a time, with explicit human confirmation before each money-moving step. - Orphaned approval detection: Checks list_refunds before acting to find approved-but-unexecuted refunds, then either completes execution or rejects them with a mandatory reason so nothing is left dangling. - Refund vs. cancellation triage: Uses receipt, payment, and cancelled-item reads to determine whether a refund is even the right action, and prevents double refunds on already-executed transactions. - Use Case: A staff member says "refund this customer's payment from yesterday." The Skill identifies the exact check, shows the amount and original payment method, confirms with the manager, then walks the refund through all three stages and verifies zero orphaned approvals remain. ## Quick Start Ask the assistant to refund a specific payment, for example: "I want to refund the payment on yesterday's receipt #1234, walk me through it safely."
