Agent skill · marketing growth · davila7
doordash-group-orders
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.
Why this skill is useful
Adds a complete executable workflow for group food ordering with DoorDash, including roster management, allergen checks, and cost splitting.
What it needs
Requires bash installed locally. Requires doordash account access. About 3k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
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. .dd/round-<date>.json — the active round's ledger: .dd/rounds.jsonl — history, one line per completed round: {"date": "...", "orderuuid": "...", "payer": "dani", "split": {"dani": 14.1, "bob": 12.4}} Flow 1 — Build a round "Order lunch for the team": 1. Roster check: load team-food.json; missing members → quick interview (hard constraints, allergens + severity, a favorite, dislikes). 2. 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. 3. 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. 4. 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. 5. Review: show the cart grouped by person with per-person subtotals. 6. Checkout: emit the checkout URL (through dd-guard if installed). The group gate hook independently re-checks allergens (see below). 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/doordash-group-orders