livespec
v0.7.4Codex Driver for livespec: thin skill bindings exposing the eight livespec operations (seed, propose-change, critique, revise, doctor, prune-history, next, help) as Codex plugin skills. The harness-neutral prose and the reference spec-side CLIs ship with livespec core (install livespec@livespec alongside this Driver).
0 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 8 skill or MCP entries
- Source updated
- Sep 6, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install livespec for Codex
codex plugin marketplace add thewoolleyman/livespec-driver-codex
codex plugin marketplace upgrade livespec-driver-codex
codex plugin add livespec@livespec-driver-codexPaste and run these commands in a terminal with Codex. They add and refresh the livespec-driver-codex catalog, then install this plugin.
Compatibility: the page URL and API slug “livespec” remain stable.
- Codex:
livespec@agent-plugin-marketplace→livespec@livespec-driver-codex
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/thewoolleyman/livespec-driver-codexClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is livespec/.
Plugin files
├── .codex-plugin/plugin.json├── skills/critique/SKILL.md├── skills/doctor/SKILL.md├── skills/help/SKILL.md├── skills/next/SKILL.md├── skills/propose-change/SKILL.md├── skills/prune-history/SKILL.md├── skills/revise/SKILL.md└── skills/seed/SKILL.md
Included Skills8
Critique 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".
Run 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 as the post-step LLM-driven phase from every wrapper-having sub-command.
Explain 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.
Rank 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 composed by a cross-repo loop driver.
File 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 reject.
Destructively 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.
Walk the user through accepting or rejecting pending proposed changes in <spec-root>/proposed_changes/, then snapshot the result as a new <spec-root>/history/vNNN/ revision. Covers every pending proposal by default, or ONE named proposal via --only-topic <topic> — leaving the rest in place — when the user asks to revise a single proposal or their authority covers only their own. Invoked by livespec:revise, "revise the livespec", "process pending proposed changes", or "revise only the <topic> proposal".
Author 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.
Plugin manifests1
{
"name": "livespec",
"version": "0.7.4",
"description": "Codex Driver for livespec: thin skill bindings exposing the eight livespec operations (seed, propose-change, critique, revise, doctor, prune-history, next, help) as Codex plugin skills. The harness-neutral prose and the reference spec-side CLIs ship with livespec core (install livespec@livespec alongside this Driver).",
"skills": "./skills/",
"hooks": "./hooks/hooks.json"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[livespec on Agent Plugins Marketplace](https://pluginsmp.com/plugins/livespec)