doordash-group-orders

Topics in the source

• DoorDash Group Orders
• State
• Flow 1 — Build a round
• Flow 2 — Paste-a-thread intake
• Flow 3 — Edits by person
• Cost split
• /whose-turn
• Rules

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. team-food.json (project dir or /.claude/dd-cli/ — committable if the team shares a repo): the roster. .dd/round- .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}} "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 w

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