DoorDash Group Orders
Coordinating N people's food is exactly the cross-session state Claude
drops: who's vegetarian, who hates cilantro, which cart line is Bob's, whose
turn it is to pay. This skill keeps a roster, attributes every cart line to
its eater, splits costs with fees prorated, and remembers payer history.
Unofficial community skill built on DoorDash's doordash-oss/doordash-cli.
Note: dd-cli orders under ONE account — the account owner pays DoorDash;
the split is for reimbursement (Venmo/transfer), not split payment.
State
team-food.json (project dir or ~/.claude/dd-cli/ — committable if the
team shares a repo): the roster.
{
"members": {
"dani": { "hard": ["vegetarian"], "allergens": [{ "name": "peanut", "severity": "anaphylaxis" }], "favorites": ["Veggie burrito bowl"], "dislikes": ["cilantro"] },
"bob": { "hard": [], "allergens": [], "favorites": ["Spicy chicken sandwich"], "dislikes": [] }
}
}
.dd/round-<date>.json — the active round's ledger:
{
"date": "2026-07-19",
"cart_uuid": "...",
"restaurant": "...",
"orders": {
"dani": [{ "item": "Veggie bowl", "cart_item_id": "41", "price": 12.5 }],
"bob": [{ "item": "Spicy chicken sandwich", "cart_item_id": "42", "price": 11.0 }]
}
}
.dd/rounds.jsonl — history, one line per completed round:
{"date": "...", "order_uuid": "...", "payer": "dani", "split": {"dani": 14.1, "bob": 12.4}}
Flow 1 — Build a round
"Order lunch for the team":
- Roster check: load
team-food.json; missing members → quick
interview (hard constraints, allergens + severity, a favorite, dislikes).
- Restaurant: intersect hard constraints (a vegetarian on the roster =
only places with real vegetarian options).
dd-cli search --query "..."
→ shortlist of 2-3 → let the human pick.
- Per-member choice: use their
favorites when the restaurant matches;
otherwise ask ONE question per member (or take answers from a pasted
thread — Flow 2). Never guess for someone with allergens.
- Build the cart:
dd-cli cart add-items ... per member's items (via
the dd-guard wrapper when doordash-spend-guard is installed). After each add,
run dd-cli cart show --cart-uuid <X> and record which cart-item-id
belongs to whom in .dd/round-<date>.json. This ledger is what makes
"quita lo de Bob" resolvable later.
- Review: show the cart grouped by person with per-person subtotals.
- Checkout: emit the checkout URL (through dd-guard if installed). The
group gate hook independently re-checks allergens (see below).
- Close the round: after the human confirms they ordered, pull the
order_uuid from
dd-cli order history, compute the split, append to
.dd/rounds.jsonl, and print a share-ready split table.
Flow 2 — Paste-a-thread intake
The user pastes a Slack/chat thread ("who wants what"). Parse it into the
round file: person → requested items. Unknown people → ask if they should
join the roster. Ambiguous requests ("something spicy") → one clarifying
question, or their favorite if the restaurant matches. Then continue Flow 1
from step 4.
Flow 3 — Edits by person
"Bob canceló" / "cambia lo de Sam": look up the person's cart_item_ids in
the round ledger, dd-cli cart remove-item --cart-uuid X --cart-item-id N
for each, update the ledger, re-show the grouped cart.
Cost split
- Item subtotals per person from the round ledger.
- Fees/tip/tax are only final on the payment page: split the known subtotal
now, and offer the post-payment fallback — "tell me the final total and
I'll prorate the difference by each person's share."
split = per-person items + prorated share of (final_total − subtotal)
when provided.
/whose-turn
Read .dd/rounds.jsonl: sum what each member has paid vs. consumed across
rounds; the next payer is the member with the largest (consumed − paid)
balance. Show the balances so the answer explains itself.
Rules
- Anyone with an
anaphylaxis allergen gets the same vetting the
doordash-allergy-shield skill applies — check their items against hidden-source
synonyms, and never guess their order.
- cart-item-ids come only from real
cart show output.
- The round ledger is the source of truth for attribution — keep it updated
on every cart mutation, or person-level edits break.
- Add
.dd/ to .gitignore unless the team explicitly wants round history
committed (it reveals eating habits).
1---
2name: doordash-group-orders
3description: "Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster. One request (\"lunch for the team\") fans out into a single merged cart with every line attributed to its eater via a person-to-cart-item-id ledger, per-person cost split with fee proration, payer rotation history, and a checkout gate that re-derives allergen conflicts against the roster live. Use when ordering for multiple people — team lunch, incident-response food, \"collect orders from the thread\" — or for /whose-turn payer rotation questions. Handles paste-a-thread intake: paste a Slack/chat thread and it builds the order ledger from it."
4allowed-tools: Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit
5tags: [DoorDash, Team Lunch, Group Orders, Cost Split, CLI, Coordination]
6metadata:
7 source: https://skillmd.com/skills/gabrielmoreira/doordash-group-orders
8---
9
10# DoorDash Group Orders
11
12Coordinating N people's food is exactly the cross-session state Claude
13drops: who's vegetarian, who hates cilantro, which cart line is Bob's, whose
14turn it is to pay. This skill keeps a roster, attributes every cart line to
15its eater, splits costs with fees prorated, and remembers payer history.
16
17> Unofficial community skill built on DoorDash's `doordash-oss/doordash-cli`.
18> Note: dd-cli orders under ONE account — the account owner pays DoorDash;
19> the split is for reimbursement (Venmo/transfer), not split payment.
20
21## State
22
23- `team-food.json` (project dir or `~/.claude/dd-cli/` — committable if the
24 team shares a repo): the roster.
25
26```json
27{
28 "members": {
29 "dani": { "hard": ["vegetarian"], "allergens": [{ "name": "peanut", "severity": "anaphylaxis" }], "favorites": ["Veggie burrito bowl"], "dislikes": ["cilantro"] },
30 "bob": { "hard": [], "allergens": [], "favorites": ["Spicy chicken sandwich"], "dislikes": [] }
31 }
32}
33```
34
35- `.dd/round-<date>.json` — the active round's ledger:
36
37```json
38{
39 "date": "2026-07-19",
40 "cart_uuid": "...",
41 "restaurant": "...",
42 "orders": {
43 "dani": [{ "item": "Veggie bowl", "cart_item_id": "41", "price": 12.5 }],
44 "bob": [{ "item": "Spicy chicken sandwich", "cart_item_id": "42", "price": 11.0 }]
45 }
46}
47```
48
49- `.dd/rounds.jsonl` — history, one line per completed round:
50 `{"date": "...", "order_uuid": "...", "payer": "dani", "split": {"dani": 14.1, "bob": 12.4}}`
51
52## Flow 1 — Build a round
53
54"Order lunch for the team":
55
561. **Roster check**: load `team-food.json`; missing members → quick
57 interview (hard constraints, allergens + severity, a favorite, dislikes).
582. **Restaurant**: intersect hard constraints (a vegetarian on the roster =
59 only places with real vegetarian options). `dd-cli search --query "..."`
60 → shortlist of 2-3 → let the human pick.
613. **Per-member choice**: use their `favorites` when the restaurant matches;
62 otherwise ask ONE question per member (or take answers from a pasted
63 thread — Flow 2). Never guess for someone with allergens.
644. **Build the cart**: `dd-cli cart add-items ...` per member's items (via
65 the dd-guard wrapper when doordash-spend-guard is installed). After each add,
66 run `dd-cli cart show --cart-uuid <X>` and record which cart-item-id
67 belongs to whom in `.dd/round-<date>.json`. This ledger is what makes
68 "quita lo de Bob" resolvable later.
695. **Review**: show the cart grouped by person with per-person subtotals.
706. **Checkout**: emit the checkout URL (through dd-guard if installed). The
71 group gate hook independently re-checks allergens (see below).
727. **Close the round**: after the human confirms they ordered, pull the
73 order_uuid from `dd-cli order history`, compute the split, append to
74 `.dd/rounds.jsonl`, and print a share-ready split table.
75
76## Flow 2 — Paste-a-thread intake
77
78The user pastes a Slack/chat thread ("who wants what"). Parse it into the
79round file: person → requested items. Unknown people → ask if they should
80join the roster. Ambiguous requests ("something spicy") → one clarifying
81question, or their favorite if the restaurant matches. Then continue Flow 1
82from step 4.
83
84## Flow 3 — Edits by person
85
86"Bob canceló" / "cambia lo de Sam": look up the person's `cart_item_id`s in
87the round ledger, `dd-cli cart remove-item --cart-uuid X --cart-item-id N`
88for each, update the ledger, re-show the grouped cart.
89
90## Cost split
91
92- Item subtotals per person from the round ledger.
93- Fees/tip/tax are only final on the payment page: split the known subtotal
94 now, and offer the post-payment fallback — "tell me the final total and
95 I'll prorate the difference by each person's share."
96- `split` = per-person items + prorated share of (final_total − subtotal)
97 when provided.
98
99## /whose-turn
100
101Read `.dd/rounds.jsonl`: sum what each member has paid vs. consumed across
102rounds; the next payer is the member with the largest (consumed − paid)
103balance. Show the balances so the answer explains itself.
104
105## Rules
106
107- Anyone with an `anaphylaxis` allergen gets the same vetting the
108 doordash-allergy-shield skill applies — check their items against hidden-source
109 synonyms, and never guess their order.
110- cart-item-ids come only from real `cart show` output.
111- The round ledger is the source of truth for attribution — keep it updated
112 on every cart mutation, or person-level edits break.
113- Add `.dd/` to `.gitignore` unless the team explicitly wants round history
114 committed (it reveals eating habits).