livespec
Claude Code Driver for livespec: thin SKILL.md bindings exposing /livespec:seed, /livespec:propose-change, /livespec:critique, /livespec:revise, /livespec:doctor, /livespec:prune-history, /livespec:next, and /livespec:help. The harness-neutral prose and the reference spec-side CLIs ship with livespec core (install livespec@livespec alongside this Driver).
Plugin livespec from marketplace livespec-driver-claude in thewoolleyman/livespec-driver-claude. Commands read from the repo's manifest — today.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
What it installs
Skills (8)
critiqueCritique an existing livespec specification or a pending proposed change, surfacing ambiguities, contradictions, and missing rules as findings the user can act on. Invoked by /livespec:critique, "critique the livespec spec", or "find issues in the spec".
doctorRun the doctor checks against a livespec spec tree — the static phase (structural failures) plus the LLM-driven objective and subjective phases — surfacing findings as JSON or as a per-finding user dialogue. Invoked by /livespec:doctor, "run livespec doctor", or "check the spec for invariants", and
helpExplain what livespec does and route the user to the right sub-command (seed, propose-change, critique, revise, doctor, prune-history). Invoked by /livespec:help, "what can livespec do", or when the user asks for an overview of livespec capabilities.
nextRank the next spec-side action (revise, propose-change, critique, prune-history, or none) over the current `<spec-target>/proposed_changes/` and `<spec-target>/history/` state, emitting structured JSON. Invoked by /livespec:next, "what should I work on next on the spec side", or as a primitive compo
propose-changeFile a proposed change against an existing livespec specification, landing it under <spec-root>/proposed_changes/<topic>.md. Invoked by /livespec:propose-change, "propose a change to the spec", or when the user wants to record a spec amendment that the next /livespec:revise pass will accept or rejec
prune-historyDestructively prune old vNNN/ snapshots from <spec-root>/history/ to bound history size. Requires explicit user invocation (model-driven invocation is disabled). Invoked only via /livespec:prune-history or an explicit "prune the livespec history" request from the user.
reviseAccept, modify, or reject pending proposed changes in <spec-root>/proposed_changes/ — confirming each with the user, or deciding under the project's configured delegated decision mode with independent review — then snapshot the result as a new <spec-root>/history/vNNN/ revision. Covers every pending
seedAuthor the initial natural-language specification for a new project, populating the chosen template's spec_root layout. Invoked by /livespec:seed, "seed a livespec spec", "set up a livespec", or when starting a brand-new spec in an empty SPECIFICATION/ tree.
Hooks (5)
- PreToolUse
/usr/bin/python3 "${CLAUDE_PLUGIN_ROOT}/hooks/pretooluse_dispatch.py"
- PreToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/block_auto_memory.py"
- PreToolUse
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/primary_checkout_playwright_guard.py"
- Stop
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/warn_plan_persistence.py"
- Stop
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/no_shadow_ledger.py"
Maintain livespec?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.