Doordash Playbook
Manage saved DoorDash order playbooks (list, add from order history, remove, inspect) stored in ~/.claude/dd-cli/playbooks.json
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/commands/doordash/doordash-playbook.md
--- allowed-tools: Bash(dd-cli:*), Bash(jq:*), Bash(cat:*), Bash(mkdir:*), Read, Write, Edit argument-hint: [list | add <name> | rm <name> | show <name>] description: Manage saved DoorDash order playbooks (list, add from order history, remove, inspect) stored in ~/.claude/dd-cli/playbooks.json --- # DoorDash Playbook Manager Manage saved order playbooks: **$ARGUMENTS** State file: `~/.claude/dd-cli/playbooks.json` (create with `mkdir -p ~/.claude/dd-cli` if missing). ## Current State - Playbooks file: !`cat ~/.claude/dd-cli/playbooks.json 2>/dev/null || echo "(no playbooks yet)"` - dd-cli available: !`command -v dd-cli || echo "dd-cli NOT on PATH"` ## Task Parse `$ARGUMENTS` and run the matching subcommand: ### `list` (default when no arguments) Render a table of playbooks: name, restaurant, baseline subtotal, contexts, last used, times used. If empty, explain how to add one. ### `add <name>` 1. Run `dd-cli order history` and show the recent orders. 2. Ask the user which order to save under `<name>` (never guess). 3. Ask for optional context words (e.g. "post-gym, workout"). 4. Write the playbook entry: `order_uuid`, `restaurant`, `items_summary` (name/qty/price per item as shown by history or the last `cart show`), `baseline_total`, `tolerance_pct: 10`, `contexts`, `last_used: today`, `times_used: 0`. ### `rm <name>` Show the entry, confirm with the user, then delete it from the JSON. ### `show <name>` Pretty-print the full entry, including stored items and baseline, and when it was last used. ## Rules - Keep the JSON valid — read-modify-write the whole file, never append text. - `order_uuid` values come only from real `dd-cli order history` output. - This command only manages the state file; actual ordering/recall flows are handled by the `doordash-order-playbooks` skill (install it alongside). - If dd-cli is missing or logged out, say so and stop — don't fabricate history entries.
Preview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: 865007e5d1c6a12668eb07074da1c363885ce31662f40bec10cc6e4ff698391f. Files are served as downloads and are never executed by this page.