What problem does it solve?
Ordering food for a team means tracking who is vegetarian, who has allergies, which cart line belongs to whom, and whose turn it is to pay — state that gets lost between sessions. This Skill maintains a persistent roster and order ledger so one request like "lunch for the team" fans out into a single merged cart with every item attributed to its eater.
Core Features & Use Cases
- Roster and round ledger: Stores member dietary constraints, allergens, and favorites in team-food.json, and tracks each cart-item-id per person in .dd/round-<date>.json so edits like "cancel Bob's item" are resolvable.
- Cost split and payer rotation: Computes per-person subtotals with prorated fees, appends completed rounds to rounds.jsonl, and answers /whose-turn by comparing paid versus consumed balances.
- Paste-a-thread intake: Parses a pasted Slack or chat thread into the order ledger, then builds the cart through dd-cli with an allergen re-check at checkout.
- Use Case: Paste your team's lunch thread from Slack, let the Skill build one DoorDash cart with each item attributed, then get a share-ready split table and a record of who paid for next time.
Quick Start
Ask the assistant to order lunch for the team using the DoorDash group orders skill and paste your team's chat thread with everyone's requests.