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.
Target: Office & team collaboration. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
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.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/doordash/doordash-group-orders/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:39.335Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.