plan-to-eat-clilisted

# plan-to-eat CLI The `plan-to-eat` CLI exposes the same 36 capabilities as the `plan-to-eat` MCP server, as subcommands. Use this skill when you have a shell but no `plan-to-eat__*` tools. **If the MCP tools *are* available, use them instead** — see the `plan-to-eat` skill. They avoid a subprocess per call and return structured JSON directly. ## Setup check ```bash plan-to-eat --version ``` **Command not found** — the CLI isn't on `PATH`. Work down this list before giving up: 1. **Run it without installing.** The CLI ships in the npm package and needs Node 18+: ```bash npx -y -p plan-to-eat-mcp@0.7.3 plan-to-eat --version # x-release-please-version ``` Note the `-p`. The package exposes two bins, and the one named `plan-to-eat-mcp` — what plain `npx plan-to-eat-mcp` resolves to — is the **MCP server**, which will sit and wait on stdio. `-p plan-to-eat-mcp plan-to-eat` is what selects the CLI. If this works, prefix every command in this skill the same way. 2. **Install it properly.** Faster than `npx` per call, and puts `plan-to-eat` on `PATH`. **Show the user this rather than running it yourself** — it writes outside the working directory: ```bash npm i -g plan-to-eat-mcp@0.7.3 # x-release-please-version ``` 3. **Working from a clone?** `node <repo>/dist/cli/main.js --version`. If `dist/` is missing, the build step was skipped — `npm install && npm run build` in the repo, then retry. 4. **Node missing entirely** (`node --version` fails) — stop a