help

help — Claude Code Driver binding

This file is the thin Claude Code binding for the help operation, shipped by the livespec-driver-claude Driver plugin (plugin name livespec, so the surface stays /livespec:*). The complete harness-neutral driving prose is livespec CORE's artifact at <core-root>/prose/help.md. FIRST resolve <core-root> (next section), THEN read that prose file in full, then execute it end-to-end, binding its harness-neutral vocabulary to this runtime as follows.

Resolving livespec core (<core-root>)

This Driver plugin ships ONLY bindings. The harness-neutral prose and the reference spec-side CLIs ship with livespec core — the livespec plugin from the thewoolleyman/livespec marketplace, which must be installed alongside this Driver. The plugin-root placeholder of THIS plugin resolves to the Driver's own root, which carries no prose/ and no scripts/ — NEVER use it for core paths. Resolve <core-root> once, in this order:

1. If the LIVESPEC_CORE_PLUGIN_ROOT environment variable is set and non-empty, use its value (explicit override; covers nonstandard dev setups, e.g. driving a sibling checkout's core).
2. If <project-root>/.claude-plugin/prose/help.md exists — the governed project IS the livespec core repo itself (--plugin-dir . dev mode / dogfooding) — use <project-root>/.claude-plugin.
3. Otherwise use the installed livespec@livespec plugin's flattened cache root, read from ~/.claude/plugins/installed_plugins.json.

Canonical Bash form (<project-root> defaults to the cwd):

LIVESPEC_CORE_ROOT="$LIVESPEC_CORE_PLUGIN_ROOT"
if [ -z "$LIVESPEC_CORE_ROOT" ] && [ -d "./.claude-plugin/prose" ]; then
  LIVESPEC_CORE_ROOT="$(pwd)/.claude-plugin"
fi
if [ -z "$LIVESPEC_CORE_ROOT" ]; then
  LIVESPEC_CORE_ROOT="$(python3 -c 'import json, pathlib; entries = json.loads((pathlib.Path.home() / ".claude" / "plugins" / "installed_plugins.json").read_text(encoding="utf-8"))["plugins"]["livespec@livespec"]; print(entries[0]["installPath"])' 2>/dev/null || true)"
fi
if [ -z "$LIVESPEC_CORE_ROOT" ] || [ ! -d "$LIVESPEC_CORE_ROOT/prose" ]; then
  echo "livespec core not found. Install it first:" >&2
  echo "  claude plugin marketplace add thewoolleyman/livespec" >&2
  echo "  claude plugin install livespec@livespec" >&2
  exit 1
fi
echo "$LIVESPEC_CORE_ROOT"

If resolution fails, STOP and surface those install instructions to the user instead of improvising paths.

Runtime bindings

• "the seed / propose-change / critique / revise / doctor / prune-history / next operation" — the corresponding /livespec:<name> skill in this Driver plugin; route the user to the slash command by that name.
• "running the seed CLI named in config with --help" — e.g. python3 "$LIVESPEC_CORE_ROOT/scripts/bin/seed.py" --help via the Bash tool (same pattern for every other operation's wrapper under $LIVESPEC_CORE_ROOT/scripts/bin/).