daily-delivery-dispatch

Assigns in-stock LionWheel delivery orders to a driver and date after stock verification.

Updated May 8, 2026
One-click install
npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill daily-delivery-dispatch-tomw200082-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: daily-delivery-dispatch
Source: https://github.com/tomw200082-collab/gt-factory-os-production-brain/tree/main/.claude/skills/daily-delivery-dispatch
Command: npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill daily-delivery-dispatch-tomw200082-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Dispatching daily delivery orders by hand means cross-checking every open order against real stock, picking the right zone and driver, and updating each task in LionWheel one at a time — slow, error-prone, and risky for live customer-facing routes. This Skill automates that entire dispatch run while keeping a human approval gate before any write. ## Core Features & Use Cases - Default-driven input resolution: Accepts just a date (e.g. "מחר") and resolves the zone from a weekday route calendar and the driver from a cached driver registry, with explicit overrides. - Stock-gated assignment: Classifies each zone order as READY or SHORT using Supabase ledger balances plus an override list, allocates limited stock oldest-first, and never partially fulfills an order. - Safe live writes with approval: Presents the exact assign/shortage plan for approval, then sets only driver_id and pickup_at via the LionWheel API — never order status — and verifies every write by re-read. - Use Case: On Wednesday evening you say "dispatch מחר"; the Skill pulls all open Center-zone orders, checks stock, shows you 14 assignable orders and a shortage list of 3 missing items, and after your "go" assigns them to the route driver for Thursday. ## Quick Start Ask the assistant to dispatch tomorrow's deliveries, for example: "Dispatch LionWheel orders for מחר" and approve the plan it presents.

Frequently Asked Questions about daily-delivery-dispatch

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

FAQPage Schema
How do I dispatch LionWheel delivery orders for a specific day?▼

Provide a date such as "מחר" or YYYY-MM-DD; the zone resolves from the weekday route calendar and the driver defaults to the route driver. The Skill lists in-stock orders for approval, then sets driver_id and pickup_at on each approved task via the LionWheel API.

How does the dispatch skill check stock before assigning orders?▼

It maps each order line SKU through the integration_sku_map table, sums calculated_on_hand from the current_balances ledger in Supabase, and allocates stock oldest-first. Items on the AVAILABLE_OVERRIDE list are treated as available; an order is READY only if every gated line is satisfiable.

Can I override the default zone or driver for a dispatch run?▼

Yes. Naming a zone explicitly overrides the route calendar, and naming a driver overrides the default route driver. If an override contradicts the calendar the Skill confirms once, and ambiguous or unknown names always trigger a question rather than a guess.

Does the LionWheel API update change order status when assigning drivers?▼

No. The write sends only driver_id and pickup_at in the PUT request to /tasks/<id>/update and never includes a status field. Each write is verified by re-reading the task to confirm the driver and date match.

What happens when an order's city is not in the zone mapping?▼

The run halts and asks which zone the city belongs to, then appends the confirmed city to zones.json so it is known next time. The Skill never guesses a city's zone, protecting orders from being misrouted.

Will dispatching affect a driver's route that is already in progress?▼

No. The Skill never modifies tasks assigned to a different driver or the target driver's tasks dated to a different day. Those orders' stock is reserved before allocation so the in-progress route stays intact.