# Clawbot/concierge menu-coverage prompt (Opus 4.8)

A prompt to verify the clawbot/concierge front-door menu surfaces the WHOLE system — every
capability videoclaw offers is on the menu and routes to a real skill/command. Authored with
the `prompting-opus-4-8` skill (enumerated scope, coverage-matrix audit, parallel fan-out,
verify-every-route-exists, audit -> plan-gate -> implement).

Run at **xhigh** effort.

```text
You're working on videoclaw-v3 (the `vclaw` CLI). The clawbot/concierge skill is the
guided front-door: it shows the user a menu of what the tool can make and routes their pick
to the right lane. The menu has fallen behind the product — I want it to cover EVERYTHING we
offer. Every capability, lane, and major command should be reachable from the menu, and every
menu option must route to a skill or command that actually exists today. Nothing we offer
should be missing, and nothing on the menu should point at a dead target.

The front-door is the concierge skill and its clawbot persona/alias. Read both
skills/concierge/SKILL.md and skills/clawbot/SKILL.md (and the standalone prompt in
docs/CONCIERGE_PROMPT.md) and keep all of them in sync — a change to the menu or routing must
land in every copy.

Ground truth for "everything we offer" is the code, not your memory. Build the full capability
inventory from: skills/catalog.json and every skills/<name>/SKILL.md, the COMMANDS array in
src/video/cli-schema.ts, `vclaw --help`, the studio goals (`vclaw studio --help` and
src/video/studio/recipes.ts / types.ts), and the handlers in src/cli/handlers/. That inventory
is the definition of "everything"; the menu is measured against it.

Do this as a coverage check. For every capability in the inventory, determine: is it reachable
from the menu (directly as an option, or clearly inside a lane the menu funnels into)? And does
the menu item that covers it route to a skill/command that exists? Produce a coverage matrix:
capability -> menu item that surfaces it -> the skill/command it routes to -> status
(COVERED / MISSING-FROM-MENU / DEAD-ROUTE / WRONG-ROUTE). Treat the inventory as exhaustive —
check every entry, don't generalize from the first few.

Find and fix:
1. MISSING: a capability/lane/command we offer that no menu option leads to. Add it to the menu
   (or fold it into the right lane) so it's reachable.
2. DEAD ROUTE: a menu option that routes to a renamed, removed, or non-existent skill/command.
   Point it at the real current target.
3. WRONG ROUTE: a menu option that funnels to the wrong lane/skill. Correct it.
4. DRIFT BETWEEN COPIES: the concierge skill, the clawbot skill, and docs/CONCIERGE_PROMPT.md
   disagree on the menu or routing. Reconcile them to one canonical menu.
5. GROUPING: the menu must stay scannable — when adding options, group by intent rather than
   exploding into a flat list of every command. Keep it usable for a novice.

Spawn parallel subagents — Opus does not fan out on its own. Dispatch subagents to build the
inventory slices concurrently (skills + catalog; the command surface from cli-schema/--help;
the studio goals; the current menu + routing in the concierge/clawbot copies) and keep working
while they run. Have them return one shared coverage matrix.

Work in two passes:
1. AUDIT (parallel): produce the coverage matrix and a short plan of what to add/fix. Show me
   the matrix and pause once for me there — adding menu items is a UX call I want to see first.
   Where the menu already covers and correctly routes a capability, say so and leave it alone.
2. UPDATE (after I approve): make the menu comprehensive. Add the missing options/lanes, fix
   dead and wrong routes, and reconcile the concierge skill, clawbot skill, and
   docs/CONCIERGE_PROMPT.md to one canonical menu. Each menu option must name (or clearly funnel
   to) the real skill/command that fulfills it. Keep the wizard's plain-language, one-step-at-a-
   time style and the plan -> preview -> spend discipline; you're completing the menu, not
   restyling the skill.

Conventions and guardrails:
- Don't reintroduce legacy paths; keep `npm run check:skill-frontdoor` green.
- If you change skills/catalog.json keep its parity test passing; run
  `npm run check:cleanroom-docs`, `npm run build`, and `npm test` before declaring done. Note
  check:release-readiness-lite has historically exited 0 even on a failing test — read the
  actual test output.

Verify before you claim done. For every menu option, confirm its routing target exists in the
code/--help you read this session, and that the concierge, clawbot, and doc copies now match.
Re-run the coverage check and confirm no capability is left MISSING-FROM-MENU (or list any you
deliberately left off and why).

When you finish, lead with the outcome — how many capabilities the menu now covers, what you
added, which routes you fixed, and that the three copies are in sync and the guardrails pass —
then the matrix detail. Plain sentences, each menu option and its target its own clause.
```