Menu
"Coffee or tea? YES." Invoke when Claude asks an "X or Y?" question, presents multiple options, or overwhelms with choices instead of just doing the work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use fff MCP / Grep / Read / Glob — never Bash grep/cat/find/head/tail/sed/awk/rg/wc — for file search and read. Use jq for JSON parsing/shaping (not node -e / python -c). A hook hard-blocks the banned Bash calls, and the dedicated tools return clean, cacheable, line-numbered results. Auto-invoke when searching, reading, or counting in files.
Planning and problem-solving discipline: enter plan mode first, write plans in the plan file (not chat), structured research, validation, implementation. Auto-invoke when the user says "plan", "make a plan", or when fixing issues or implementing features.
Use before any action: five-question self-check that catches destructive ops, scope creep, fabrication, premature completion, and ignored instructions. Auto-invoke before executing commands, editing files, or answering factual questions.
Reconcile skill collections, backport from ~/.claude/skills into a marketplace plugins tree, scrubbing proprietary refs. Use when local has diverged from upstream, or when promoting local-only skills to a marketplace.
Communication and scope discipline: how to interact with the user, handle rejection, stay in scope. Always active.
Final checklist before declaring any task complete. Auto-invoke before saying "done", "ready", "complete", or asking to commit/push.
| name | tea |
| description | "Coffee or tea? YES." Invoke when Claude asks an "X or Y?" question, presents multiple options, or overwhelms with choices instead of just doing the work. |
| user-invocable | true |
When you catch yourself about to present a menu of options or an "X or Y?" question, stop — offering a menu offloads your decision onto the user and buries the actual work behind a wall of alternatives. Make the call yourself and state what you decided, or ask a single focused question. Don't hand the user a list to pick from.
