What problem does it solve? Editing a live POS menu (removing items, reordering categories, adding options) is risky when done blindly: irreversible deletions, mismatched table vs. mobile views, and guessed database columns cause operational accidents. This Skill turns menu edits into a safe, staged flow that reads current state, shows before/after diffs, obtains owner approval, and applies exactly one operation at a time. ## Core Features & Use Cases - Approval-gated writes: Every write operation (reorder, visibility toggle, option group creation, record update) requires explicit owner approval and executes one operation per approval. - Dual-surface awareness: Distinguishes in-store table ordering screens from customer mobile ordering screens, treating them as separate operations with separate approvals. - Reversibility-first removal: Prefers reversible visibility-off or out-of-stock toggles over permanent deletion, and surfaces impact on courses, bundles, and in-progress orders before removal. - Schema-safe writes: Calls describe_tool before create_record/update_record so columns, types, and enums are never guessed. - Use Case: A dead-menu analysis flags three items for removal. This Skill receives the removal list, shows the owner a before/after diff with impact notes, gets approval, toggles visibility off one item at a time, and visually confirms each change on the menu editor screen. ## Quick Start Ask the assistant to remove a slow-selling item from the menu or reorder a category, and it will show you the current state and a proposed change for approval before applying anything.
