What problem does it solve? Working in Kinaxis RapidResponse / Maestro, it is easy to confuse a safe what-if simulation with an action that changes the shared plan or releases real orders to ERP. This Skill gives the judgment to classify every Kinaxis operation as read, reversible write, committing write, or destructive, so consequential actions like commit, publish, and release are gated for human approval. ## Core Features & Use Cases - Operation classification matrix: Maps Kinaxis operation families (scenario edits, commits, publishes, CTP confirms, automation chains) to read / write / destructive risk classes with gating rules. - Scenario and commit semantics: Explains copy-on-write scenario deltas, parent inheritance, private vs public scenarios, and why commit is one-directional with no clean uncommit. - Recovery playbooks: Covers undo paths from discarding a private scenario up to canceling released orders in ERP, including freshness checks before any commit. - Use Case: A planner needs to pull in 500 units for a new order. The Skill walks them through forking a private scenario, re-planning safely, verifying ERP sync freshness, then committing and releasing with dependents only after human approval. ## Quick Start Ask the assistant how to safely commit a Kinaxis scenario and release its planned orders to ERP without affecting the shared baseline.
