메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
Classifies shipment delay severity (SD-DELAY-001 minor / SD-DELAY-002 severe) and ranks expedite / split-ship / reschedule options. Triggered on DELIVERY_DELAY events.
Detects and classifies Duplicate Purchase Order (PO) exceptions in B2B order intake. Triggered on EDI_850_DUPLICATE_PO events.
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.
| name | edi-mismatch |
| description | 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. |
| metadata | {"version":"1.0.0","author":"CPG Expert-Systems-Architect","required_tools":["mcp-buyer-notification"],"recipes":["EdiMismatchRecipe.py"],"constrained_generation":["Guidance","Outlines"]} |
This skill handles EDI 850 line-level mismatches against the master record:
SKU, quantity, unit-of-measure, and ship-to. Each sub_type has a
deterministic classification branch in EdiMismatchRecipe.py — SKU
mismatches hard-reject, qty / UOM require buyer confirmation, and ship-to
escalates.
PRICE_MISMATCH is not handled here. An EDI 850 line mismatch whose
field is price is re-routed at classifier time to CONTRACTUAL_CORRECTION
and executes PriceAdjustmentRecipe.py, keeping pricing the single source
of truth (CLAUDE.md §1). The skill loader and the deterministic-fallback
classifier both fork on event.metadata.mismatch_sub_type so a PRICE
mismatch is statically impossible to reach this skill.
EDI_850_LINE_MISMATCH.event.metadata.mismatch_sub_type. Never infer the sub_type — if
missing, fail to human.mismatch_sub_type ∈ AllowedEdiMismatchSubType (SKU, QTY, UOM,
SHIP_TO). If equal to PRICE_MISMATCH, this skill should never have been
loaded — raise a routing-invariant failure.EDI_MISMATCH.EdiMismatchRecipe.py — the only allowed recipe for this intent.Use Guidance / Outlines for all machine-consumed outputs:
EDI_MISMATCHEdiMismatchRecipe.pysub_type constrained to AllowedEdiMismatchSubTypeclassification constrained to AllowedEdiMismatchClassification
(HARD_REJECT / REVIEW / ESCALATE)EdiMismatchRecipe.pymismatch_sub_type == PRICE_MISMATCH → handled by PriceAdjustmentRecipe.py
via the CONTRACTUAL_CORRECTION path (routed at classifier time).Compliance Shadow runs before the recipe. Verdicts are sub_type-aware:
The recipe itself is pure classification — no I/O, no side effects. The downstream buyer-notification effect is applied by orchestration after the recipe returns, not by the recipe.
The Recipe Execution Log must capture:
sub_typeclassification (HARD_REJECT | REVIEW | ESCALATE)recommended_action (BLOCK_AND_NOTIFY | REQUEST_BUYER_CONFIRMATION | ESCALATE)autonomy_level (L1 / L2 / L3)expected_value and received_value (for audit)