doordash-order-playbooks

Topics in the source

• DoorDash Order Playbooks
• Why this exists
• State
• Preflight (first use only — REQUIRED)
• Flow 1 — Recall (the main flow)
• Flow 2 — Capture
• Flow 3 — Staleness / self-heal
• Rules

Saved orders with names and contexts, recalled safely. A playbook maps a human name ("post-gym", "late-night deploy", "Friday ramen") to a concrete DoorDash order that can be rebuilt with dd-cli order reorder — plus enough stored detail to detect drift (menu changes, price hikes, substitutions) before the user is ever handed a checkout link. Unofficial community skill built on DoorDash's doordash-oss/doordash-cli. dd-cli must be installed, on PATH, and logged in (dd-cli login). dd-cli order history already lists past orders — but Claude has no cross-session memory of which order is "the post-gym one", and plain reordering silently accepts whatever the restaurant's menu says today: substituted items, missing items, higher prices. This skill stores the mapping AND makes a cart-diff against the stored baseline mandatory before emitting any checkout URL. Silent drift becomes a caught event. Single JSON file: /.claude/dd-cli/playbooks.json Create the directory and file on first use (mkdir -p /.claude/dd-cli). Prices are pre-fee subtotals — say so when presenting totals. This skill assumes dd-cli order reorder --order-uuid Y returns a cart-uuid that cart show and order checkout-url accep

This is an excerpt. Refer to the complete source and its current requirements.