What problem does it solve? Oracle Agile PLM controls the released product baseline that manufacturing and procurement build and buy against, and actions like releasing an ECO, re-pointing an AML via an MCO, or issuing a stop ship can silently re-point sourcing or halt production with no revision bump to signal the change. This Skill gives an AI agent the operator judgment to classify every Agile action as read, write, or destructive and to pause consequential ones for human approval. ## Core Features & Use Cases - Action classification and gating: Maps Agile operation families (item/revision reads, redline edits, change release, MCO/SCO sourcing changes, stop ship, obsolete/supersede) to read / write-reversible / write-committing / destructive gates. - Agile-specific edge-state handling: Covers change-driven revisioning (no standalone Revise), Pending vs Released revisions, MCO/SCO/PCO no-rev traps, site overrides, file folder versioning, effectivity, and PG&C compliance rollups. - Recovery playbooks: Provides forward-path recovery patterns, such as correcting a wrong effectivity with a new ECO and re-publish rather than de-releasing a change. - Use Case: When asked to swap a preferred manufacturer part on a released item, the agent recognizes this as an MCO that re-points procurement with no rev bump, runs Where Used, and gates the release for named human approval instead of treating it as routine housekeeping. ## Quick Start Ask the agent to release an ECO that revises bracket BRK-100 to rev C with effectivity limited to units 5000 and above, and have it classify and gate each step.
