← ClaudeAtlas

ccc-morelisted

CC Commander second-page menu — click-first access to plan, x-ray, Linear, fleet, connect, and catalog browse. Use when the user types /ccc-more, picks 'More tools'…
KevinZai/commander · ★ 3 · AI & Automation · score 79
Install: claude install-skill KevinZai/commander
# /ccc-more — Second-page tools menu Click-first picker for the CC Commander surface area that's NOT build/review/ship/design/learn. Plan, x-ray, Linear, fleet, connect, browse — one click each, cascade for the long tail. ## Response shape (EVERY time) ### 1. Brand header (one line) ``` **CC Commander · More** · 7 tools · [all commands](https://commanderplugin.com/commands) ``` ### 2. Context strip (one line) Parallel Bash probe (silent on failure): - `test -f tasks/todo.md && wc -l tasks/todo.md` — open tasks - `git rev-parse --abbrev-ref HEAD 2>/dev/null` — branch - `claude mcp list 2>/dev/null | grep -c '^ '` — connected MCPs - `test -f .linear/config.json && echo linear-ok` — Linear wired Render: > 🧭 Branch `<name>` · <N> open tasks · <M> MCPs connected · Linear: `<connected | not set up>` If barely any context: "🧭 Empty-ish project — Plan a feature or run X-ray to get signal." ### 3. The picker — `AskUserQuestion` page 1 Read `${CLAUDE_PLUGIN_ROOT}/menus/ccc-more.json` once. Use its `choices`. **Max 4 options** — 3 headline tools + "Even more…". ``` question: "Which tool?" header: "CC Commander · More" multiSelect: false options: - label: "📋 Plan a feature" description: "Spec interview → implementation plan file → review checkpoint." preview: "Invokes ccc-plan. Asks 5-7 targeted questions — writes to the session plan file (shows in Desktop Plan pane)." - label: "🩻 Project x-ray" description: "Scorecard across code, docs, tests, deps, CI —