What problem does it solve? Floor staff requests like "move this table", "combine two tables", or "reset this table" sound similar but map to very different POS operations—some reversible, some permanently merging or destroying order tickets. This Skill prevents costly mistakes by reading the live floor state first, distinguishing reversible grouping from irreversible merging, and requiring explicit human confirmation before each write operation. ## Core Features & Use Cases - Intent disambiguation: Maps vague requests to the correct operation—move (reversible), group (reversible), merge (irreversible), or force-clear (last resort)—instead of acting on literal wording. - Billing consolidation transparency: Always states which table becomes the primary billing target and whether tickets stay separate or merge into one before executing. - Safety gates: Requires one confirmation per operation, treats force_clear_table as a last resort after normal checkout routes, and escalates on permission (422) rejections. - Use Case: A server says "combine tables 3 and 5 for one check." The Skill reads open sessions and the floor map, proposes reversible grouping with billing consolidated to table 3, gets confirmation, executes, then re-reads the floor map to verify. ## Quick Start Ask the assistant to move the party at table 4 to table 8 and combine tables 2 and 3 into one group for a single check, confirming each step before it runs.
