القائمة
Classifies shipment delay severity (SD-DELAY-001 minor / SD-DELAY-002 severe) and ranks expedite / split-ship / reschedule options. Triggered on DELIVERY_DELAY events.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Classifies a post-extraction email-channel sales-order envelope into one-click approve, standard review, low-confidence, or fatal-reject. Triggered on EMAIL_ORDER_ENTRY_REQUEST events.
Triaged a back-order / out-of-stock condition on an inbound order line and ranks resolution options — alternate DC, substitute SKU, split shipment, or reschedule. Triggered on BACK_ORDER_OOS events.
Detects and classifies Duplicate Purchase Order (PO) exceptions in B2B order intake. Triggered on EDI_850_DUPLICATE_PO events.
Classifies non-duplicate EDI 850 line mismatches (SKU, qty, UOM, ship-to) and selects the appropriate resolution path. Triggered on EDI_850_LINE_MISMATCH events whose metadata.mismatch_sub_type is not PRICE_MISMATCH.
Decides whether to round a PO line up to the Minimum Order Quantity, accept below MOQ, or escalate for a KNMT waiver. Triggered on MIN_ORDER_QTY events.
Classifies a PO whose total quantity exceeds the contract max and recommends a per-line trim plan that preserves pallet integrity where possible. Triggered on OVER_MAX_QTY events.
استنادا إلى تصنيف SOC المهني
| name | delivery-delay |
| description | Classifies shipment delay severity (SD-DELAY-001 minor / SD-DELAY-002 severe) and ranks expedite / split-ship / reschedule options. Triggered on DELIVERY_DELAY events. |
| metadata | {"version":"1.0.0","author":"CPG Expert-Systems-Architect","required_tools":["mcp-oms-connector","mcp-carrier-integration"],"recipes":["DeliveryDelayResolutionRecipe.py"],"constrained_generation":["Guidance","Outlines"]} |
Triggered when a shipment's projected ETA slips past the planned
delivery date. The skill classifies the delay as MINOR or SEVERE and
ranks alternate options (EXPEDITE, SPLIT_SHIP, RESCHEDULE). Days-late
thresholds live in DeliveryDelayResolutionRecipe.py and are
policy-injected from contracts/policy.py.
DELIVERY_DELAY.metadata.planned_date, metadata.projected_eta, optionally
metadata.alternate_options / delay_category / carrier /
route.DELIVERY_DELAY.DeliveryDelayResolutionRecipe.py.DELIVERY_DELAYDeliveryDelayResolutionRecipe.pyGREEN | YELLOW | REDEXPEDITE | SPLIT_SHIP | RESCHEDULE
plus caller-supplied variants); no UI dispatch on the value.DeliveryDelayResolutionRecipe.pyFAIL_TO_HUMANDELIVERY_DELAY_MINOR_DAYS).DELIVERY_DELAY_SEVERE_DAYS); reschedule /
buyer notification mandatory. For SEVERE delays the option ranker
prefers RESCHEDULE over EXPEDITE to avoid expensive last-mile work.days_late, delay_categoryclassification (ON_TIME | MINOR_DELAY | SEVERE_DELAY)primary_option + full alternate_options[]recommended_action (EXPEDITE | SPLIT_SHIP | RESCHEDULE | NO_ACTION)