recall-execution

Coordinates lot genealogy tracing, quarantine holds, and field pulls for product recalls.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill recall-execution-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recall-execution
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/business-workflows/recall-execution
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill recall-execution-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a defect or contamination is confirmed on specific lots, every downstream location holding affected product must be traced, quarantined, and pulled on a regulator clock with a provably complete trail. This Skill coordinates that multi-system recall response without letting the agent decide scope, pull stock, or notify regulators on its own. ## Core Features & Use Cases - Forward genealogy closure: Traces flagged input lots through PLM/BOM and ERP batch-where-used records to every affected finished lot, including repacks, relabels, and shared root causes. - Where-distributed mapping: Reconciles units produced against DCs, customer sites, in-transit shipments, consignment/VMI stock, and samples so no node is missed. - Gated execution: Every committing write (lot blocks, WMS holds, pull orders, reverse pickups, recall register) and every outbound notice (customer, regulator) holds for human approval, with destruction requiring a separate disposition sign-off. - Use Case: A sterile injectable lot is confirmed contaminated. The agent closes the genealogy to 5 finished lots, maps 61,200 vials across 243 nodes, prices full-pull versus phased options, and presents a Class I recommendation to the quality head for approval before fanning out tasks. ## Quick Start Ask the agent to scope and coordinate a recall for the confirmed contaminated lots, tracing all affected finished products and drafting the holds and notices for approval.

Frequently Asked Questions about recall-execution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace affected lots in a product recall?

Trace forward from the confirmed input lots through batch-where-used records in PLM/BOM and ERP to the transitive closure of finished lots. Follow repacks and relabels, and check one hop up for shared root causes like a common raw material, line, or time window.

How do I build a where-distributed map for a recall?

Read shipment and delivery records per finished lot to get units by node: DC on-hand, customer sites, retail, and in-transit. Reconcile units produced against all locations, and include consignment/VMI stock, samples, and further-manufactured B2B destinations that on-hand snapshots miss.

Can the agent notify regulators or customers automatically during a recall?

No. Customer notices and regulator submissions are high-egress actions that require explicit human sign-off on the wording. The agent drafts and tracks them, but the regulatory head files the submission.

What happens if the recall scope is wrong?

Under-scoping misses affected product and is treated as a safety failure; over-scoping adds logistics cost and supply disruption. A scope widening is handled as a recall expansion with re-tracing, a supplemental regulator notice on its own clock, and a fresh approval gate.

When is a recall considered complete?

A recall closes when accounted units (returned, quarantined, destroyed with proof, or documented-consumed) meet the effectiveness threshold for the recall class, such as Level A requiring 100% of consignees contacted. It stays open while any affected node is unaccounted.