DoorDash Order Playbooks
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).
Why this exists
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.
State
Single JSON file: ~/.claude/dd-cli/playbooks.json
{
"playbooks": {
"post-gym": {
"order_uuid": "<uuid from dd-cli order history>",
"restaurant": "Sweetgreen",
"items_summary": [
{ "name": "Harvest Bowl", "qty": 1, "price": 13.95 },
{ "name": "Lemonade", "qty": 1, "price": 3.5 }
],
"baseline_total": 17.45,
"tolerance_pct": 10,
"contexts": ["post-gym", "gym", "workout"],
"last_used": "2026-07-19",
"times_used": 4
}
},
"preflight": { "verified": false, "notes": "" }
}
Create the directory and file on first use (mkdir -p ~/.claude/dd-cli).
Prices are pre-fee subtotals — say so when presenting totals.
Preflight (first use only — REQUIRED)
This skill assumes dd-cli order reorder --order-uuid Y returns a cart-uuid
that cart show and order checkout-url accept. That handoff is
load-bearing and must be verified empirically once per install:
- Run
dd-cli order reorder --help and dd-cli order checkout-url --help
to confirm flags.
- On the first real recall, after running
reorder, confirm the output
contains a cart-uuid and that dd-cli cart show --cart-uuid <it> works.
- Record the outcome in
preflight.verified (+ any format notes in
preflight.notes) so future sessions skip this step.
If the handoff does NOT work as assumed, fall back to rebuilding the cart
manually (dd-cli search → cart add-items) and record that in
preflight.notes.
Flow 1 — Recall (the main flow)
User says something like "order my post-gym bowl" / "the usual after the gym":
Match: fuzzy-match the request against playbook names and contexts.
Ambiguous → ask. No match → offer Flow 2 (capture) instead.
Rebuild: dd-cli order reorder --order-uuid <stored uuid>. Capture
the cart-uuid from the output.
MANDATORY diff: run dd-cli cart show --cart-uuid <cart-uuid> and
compare against the stored items_summary + baseline_total:
|
Stored |
Current |
| Harvest Bowl |
$13.95 |
$14.95 ⬆ |
| Lemonade |
$3.50 |
❌ missing |
| Subtotal |
$17.45 |
$14.95 |
Present the diff table to the user. Never skip this step, even when
everything matches — say "matches your baseline" explicitly.
Gate: if items are missing/substituted, or the subtotal exceeds
baseline_total by more than tolerance_pct, STOP and ask the user how
to proceed (accept, edit cart via cart remove-item/cart add-items, or
abort). Do NOT hand over a checkout link silently.
Checkout: only after the diff is shown (and approved when the gate
tripped): dd-cli order checkout-url --cart-uuid <cart-uuid>. Hand the
URL to the user — payment always happens on the DoorDash page, by the
human.
Update: bump last_used / times_used; if the user accepted new
prices, offer to refresh items_summary and baseline_total.
Flow 2 — Capture
After ANY completed order (via playbook or bespoke), offer once — don't nag:
"Want to save this as a playbook?" If yes:
dd-cli order history — take the most recent order's uuid.
- Ask for a name and optional context words ("when should I suggest this?").
- Write the entry with
items_summary and baseline_total from the cart
that was just built (or from the history entry if it shows detail).
- Default
tolerance_pct: 10.
Flow 3 — Staleness / self-heal
When order reorder fails or the diff shows the restaurant no longer offers
the stored items:
- Tell the user the playbook is stale and why.
dd-cli search --query "<restaurant name>" — confirm the restaurant still
exists on DoorDash. Gone → offer to retire the playbook or find a
replacement.
- Rebuild an equivalent cart (
cart add-items, navigating with --help as
needed), confirm with the user, and after a successful checkout-url
handoff refresh the playbook's order_uuid from dd-cli order history.
Rules
- Never emit a checkout URL without showing the diff first. This is the
contract of the skill.
- Read uuids from real command output; never fabricate or guess them.
- One capture offer per order, max. Respect a "no".
- Totals you can verify are pre-fee subtotals; final totals (fees, tip, tax)
appear only on the DoorDash payment page. Say so.
- If
dd-cli reports auth/waitlist errors, stop and tell the user to run
dd-cli login — don't retry in a loop.
1---
2name: doordash-order-playbooks
3description: Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over. Use when the user names a saved order ("order my post-gym bowl", "the usual", "my Friday ramen"), wants to save the order they just placed as a playbook, or asks to list/remove saved orders. Persists name→order-uuid playbooks across sessions, catches silent menu/price drift on every recall, and self-heals stale playbooks when a restaurant's menu changes. Requires dd-cli (macOS Apple Silicon, waitlist-gated).
4allowed-tools: Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit
5tags: [DoorDash, Food Delivery, CLI, Saved Orders, Reorder, Automation]
6metadata:
7 source: https://skillmd.com/skills/gabrielmoreira/doordash-order-playbooks
8---
9
10# DoorDash Order Playbooks
11
12Saved orders with names and contexts, recalled safely. A playbook maps a
13human name ("post-gym", "late-night deploy", "Friday ramen") to a concrete
14DoorDash order that can be rebuilt with `dd-cli order reorder` — plus enough
15stored detail to **detect drift** (menu changes, price hikes, substitutions)
16before the user is ever handed a checkout link.
17
18> Unofficial community skill built on DoorDash's `doordash-oss/doordash-cli`.
19> `dd-cli` must be installed, on PATH, and logged in (`dd-cli login`).
20
21## Why this exists
22
23`dd-cli order history` already lists past orders — but Claude has no
24cross-session memory of *which* order is "the post-gym one", and plain
25reordering silently accepts whatever the restaurant's menu says *today*:
26substituted items, missing items, higher prices. This skill stores the
27mapping AND makes a cart-diff against the stored baseline **mandatory**
28before emitting any checkout URL. Silent drift becomes a caught event.
29
30## State
31
32Single JSON file: `~/.claude/dd-cli/playbooks.json`
33
34```json
35{
36 "playbooks": {
37 "post-gym": {
38 "order_uuid": "<uuid from dd-cli order history>",
39 "restaurant": "Sweetgreen",
40 "items_summary": [
41 { "name": "Harvest Bowl", "qty": 1, "price": 13.95 },
42 { "name": "Lemonade", "qty": 1, "price": 3.5 }
43 ],
44 "baseline_total": 17.45,
45 "tolerance_pct": 10,
46 "contexts": ["post-gym", "gym", "workout"],
47 "last_used": "2026-07-19",
48 "times_used": 4
49 }
50 },
51 "preflight": { "verified": false, "notes": "" }
52}
53```
54
55Create the directory and file on first use (`mkdir -p ~/.claude/dd-cli`).
56Prices are pre-fee subtotals — say so when presenting totals.
57
58## Preflight (first use only — REQUIRED)
59
60This skill assumes `dd-cli order reorder --order-uuid Y` returns a cart-uuid
61that `cart show` and `order checkout-url` accept. That handoff is
62load-bearing and must be verified empirically once per install:
63
641. Run `dd-cli order reorder --help` and `dd-cli order checkout-url --help`
65 to confirm flags.
662. On the first real recall, after running `reorder`, confirm the output
67 contains a cart-uuid and that `dd-cli cart show --cart-uuid <it>` works.
683. Record the outcome in `preflight.verified` (+ any format notes in
69 `preflight.notes`) so future sessions skip this step.
70
71If the handoff does NOT work as assumed, fall back to rebuilding the cart
72manually (`dd-cli search` → `cart add-items`) and record that in
73`preflight.notes`.
74
75## Flow 1 — Recall (the main flow)
76
77User says something like "order my post-gym bowl" / "the usual after the gym":
78
791. **Match**: fuzzy-match the request against playbook names and `contexts`.
80 Ambiguous → ask. No match → offer Flow 2 (capture) instead.
812. **Rebuild**: `dd-cli order reorder --order-uuid <stored uuid>`. Capture
82 the cart-uuid from the output.
833. **MANDATORY diff**: run `dd-cli cart show --cart-uuid <cart-uuid>` and
84 compare against the stored `items_summary` + `baseline_total`:
85
86 | | Stored | Current |
87 |---|---|---|
88 | Harvest Bowl | $13.95 | $14.95 ⬆ |
89 | Lemonade | $3.50 | ❌ missing |
90 | **Subtotal** | **$17.45** | **$14.95** |
91
92 Present the diff table to the user. Never skip this step, even when
93 everything matches — say "matches your baseline" explicitly.
944. **Gate**: if items are missing/substituted, or the subtotal exceeds
95 `baseline_total` by more than `tolerance_pct`, STOP and ask the user how
96 to proceed (accept, edit cart via `cart remove-item`/`cart add-items`, or
97 abort). Do NOT hand over a checkout link silently.
985. **Checkout**: only after the diff is shown (and approved when the gate
99 tripped): `dd-cli order checkout-url --cart-uuid <cart-uuid>`. Hand the
100 URL to the user — payment always happens on the DoorDash page, by the
101 human.
1026. **Update**: bump `last_used` / `times_used`; if the user accepted new
103 prices, offer to refresh `items_summary` and `baseline_total`.
104
105## Flow 2 — Capture
106
107After ANY completed order (via playbook or bespoke), offer once — don't nag:
108"Want to save this as a playbook?" If yes:
109
1101. `dd-cli order history` — take the most recent order's uuid.
1112. Ask for a name and optional context words ("when should I suggest this?").
1123. Write the entry with `items_summary` and `baseline_total` from the cart
113 that was just built (or from the history entry if it shows detail).
1144. Default `tolerance_pct`: 10.
115
116## Flow 3 — Staleness / self-heal
117
118When `order reorder` fails or the diff shows the restaurant no longer offers
119the stored items:
120
1211. Tell the user the playbook is stale and why.
1222. `dd-cli search --query "<restaurant name>"` — confirm the restaurant still
123 exists on DoorDash. Gone → offer to retire the playbook or find a
124 replacement.
1253. Rebuild an equivalent cart (`cart add-items`, navigating with `--help` as
126 needed), confirm with the user, and after a successful checkout-url
127 handoff refresh the playbook's `order_uuid` from `dd-cli order history`.
128
129## Rules
130
131- **Never emit a checkout URL without showing the diff first.** This is the
132 contract of the skill.
133- Read uuids from real command output; never fabricate or guess them.
134- One capture offer per order, max. Respect a "no".
135- Totals you can verify are pre-fee subtotals; final totals (fees, tip, tax)
136 appear only on the DoorDash payment page. Say so.
137- If `dd-cli` reports auth/waitlist errors, stop and tell the user to run
138 `dd-cli login` — don't retry in a loop.