LiveSpec Driver Claude
thewoolleyman/livespec-driver-claude
Driver Claude para o ciclo de vida de especificações livespec
Ver no GitHubSkill que integra Claude Code com livespec, fornecendo oito comandos `/livespec:*` para gerenciar o ciclo de vida de especificações. Funciona como driver agnóstico de orquestrador, delegando operações substantivas ao núcleo livespec enquanto expõe apenas bindings finos de código.
Instalação
npx convez-ai thewoolleyman/livespec-driver-claude1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Criar e iterar especificações de projeto com linguagem natural
- Propor, revisar e revisar mudanças em especificações existentes
- Validar especificações com análise estática e orientada por LLM
- Gerenciar histórico de versões e priorizar próximas ações de spec
Veredito

Ferramenta especializada e bem arquitetada para equipes que adotam livespec como framework de especificação. Exige entendimento profundo do ecossistema livespec e funciona melhor em fluxos de trabalho colaborativos estruturados; não é apropriada para uso casual.
README
A tradução para o português deste README ainda está na fila.
livespec-driver-claude
The Claude Code Driver for livespec
— the first reference Driver under livespec's contract + reference
implementations architecture (per livespec SPECIFICATION/spec.md
§"Contract + reference implementations architecture").
A Driver is the thin, agent-runtime-specific wrapper through which a human drives the spec lifecycle interactively. This repo ships ONLY the thin Claude Code SKILL.md bindings for the eight spec-side operations. Everything substantive stays in livespec core:
| Artifact | Ships with |
|---|---|
Harness-neutral driving prose (prose/<name>.md) | livespec core |
Reference spec-side CLIs (scripts/bin/<name>.py) | livespec core |
| JSON schemas, templates | livespec core |
Thin /livespec:* Claude Code bindings | this repo |
The Driver binds core's prose and config-named CLIs only. It has ZERO dependencies on any orchestrator (the load-bearing Driver ↔ orchestrator zero-dependency invariant).
Install
Both plugins are required — core carries the prose and CLIs, this
Driver carries the /livespec:* commands:
/plugin marketplace add thewoolleyman/livespec
/plugin install livespec@livespec
/plugin marketplace add thewoolleyman/livespec-driver-claude
/plugin install livespec@livespec-driver-claude
After install, restart Claude Code (or run /reload-plugins). The
eight slash commands become available with the livespec: namespace
prefix (the Driver plugin is deliberately NAMED livespec so the
established /livespec:* surface is preserved):
/livespec:seed— author the initial natural-language spec/livespec:propose-change— file a proposed change against the spec/livespec:critique— surface issues in the spec/livespec:revise— accept or reject pending proposed changes/livespec:doctor— run static + LLM-driven validation/livespec:prune-history— collapse oldhistory/vNNN/entries/livespec:next— rank the next spec-side action/livespec:help— overview + routing to the right sub-command
How the bindings find livespec core
Each SKILL.md resolves the livespec core plugin root (<core-root>)
at runtime, in order:
- the
LIVESPEC_CORE_PLUGIN_ROOTenvironment variable (explicit override); <project-root>/.claude-plugin/prose/when the governed project IS the livespec core repo (--plugin-dir .dev mode / dogfooding);- the installed
livespec@livespecplugin's flattened cache root, read from~/.claude/plugins/installed_plugins.json.
It then reads <core-root>/prose/<name>.md (the harness-neutral
driving prose) and dispatches the operation's CLI as named in the
governed project's .livespec.jsonc spec_clis section (argv-form,
pre-populated with core's reference defaults, individually
overridable per livespec contracts.md §"Spec-side CLI contract").
Development
just bootstrap # one-time: primary-checkout guard hooks + lefthook + plugins
just check # full enforcement aggregate (manifests, skills, lint, e2e)
The repo follows the livespec-family conventions: .mise.toml pins
the non-Python binaries (uv, just, lefthook), the justfile is the
single entry point for every check, lefthook delegates to just, and
the primary checkout refuses direct commits (work happens in
git worktree add secondaries).
Backlog
This repo's backlog lives in its beads tenant
(livespec-driver-claude on the shared dolt-server) — query it with
bd list. BACKLOG.md is a pointer recording the founding
items' migration provenance.
Observability
The livespec family dogfoods its own telemetry. CI runs, Red→Green commit-gate cycles, the beads+fabro dispatcher, sandbox runs, and harness sub-agents are published to a shared Honeycomb environment:
- livespec family — all activity — the cross-repo activity board (Honeycomb,
livespecenvironment).