What plans are in flight?
See a feature’s plans, finished steps, and next open step before you start or resume work.
Vaultspec implements a structured coding workflow focused on #features, decision records, and the documents grounding them. Its rules, skills, and agents guide your coding agent through each step, and its CLI and MCP server scaffold, validate, and link the documents.
Each feature moves through five steps, from research to review, and every step writes its record to the project's own .vault/ folder. The steps pay off when a feature needs research and a choice between architectural options before code is written. Small fixes don't need the full pipeline.
tags tie together the pipeline's steps
The research, decisions, and plan live in your vault as Markdown files, not in one provider's chat history, so another agent can read them and pick up where the last one stopped.
› Can we implement a new calendar module displaying past release dates, with a month and year switcher and filters?Recording deferred.
› Can we implement a new calendar module displaying past release dates, with a month and year switcher and filters?Recording deferred.
› Can we implement a new calendar module displaying past release dates, with a month and year switcher and filters?Recording deferred.
Agents write the prose; the tools scaffold each document, validate its metadata and structure, and keep the links between documents intact. Those links give every feature a history of its decisions, execution records, and related features.
See a feature’s plans, finished steps, and next open step before you start or resume work.
Find broken links, invalid metadata, and structural errors. Add --fix to correct the ones that can be fixed automatically.
Search by what the code does, in plain words. Add --type code to leave documents out.
$ vaultspec-core status search-indexRecording deferred.
$ vaultspec-core vault check allRecording deferred.
$ vaultspec-rag search "fail the page if it invents customers testimonials or pricing" --type code --limit 1 --scoresRecording deferred.
Tell agents which step comes next and which skill or agent handles it.
Walk an agent through each step and the document it produces, from research to review.
Specialized personas that research, plan, implement, and review within the framework.
Run conformance and quality checks on the vault documents a session produces.
Each project's current release in full, and the releases before it, taken from the published changelogs when this site was built.
cimake release proposal checks ready without manual approvalcistart the proven release when its proposal mergesvaultspec-core sets up the harness in your repository. vaultspec-rag is optional, but the workflow is designed around it: it adds semantic search over your code and documents, and installs vaultspec-core with it.
Python installs require CPython 3.13 or 3.14 on macOS, Linux, or Windows. With uv, a supported interpreter is downloaded if needed. Standalone binaries need no separate Python installation.
From PyPI, with uv or pip
Runs in a cached, isolated environment. Reuse the command prefix for later commands.
uvx vaultspec-core installInstalls the command on your PATH for repeated use.
uv tool install vaultspec-coreAdds a project dependency. Contributors install it with uv sync and run commands through uv run.
uv add vaultspec-coreuv run vaultspec-core installInstalls Core from PyPI with pip. Install uv too: the generated agent launchers use uv or uvx.
pip install vaultspec-coreWith Homebrew, on macOS and Linux
brew install nevenincs/tap/vaultspec-coreApple silicon macOS, and x86_64 and arm64 Linux.
With Scoop, on Windows
scoop bucket add nevenincs https://github.com/nevenincs/homebrew-tapscoop install nevenincs/vaultspec-coreStandalone binaries, no Python installation needed
| Platform | vaultspec-core |
|---|---|
| macOS · Apple silicon | vaultspec-core-v0.3.7-aarch64-apple-darwin.tar.gz |
| Linux · x86_64 | vaultspec-core-v0.3.7-x86_64-unknown-linux-gnu.tar.gz |
| Linux · arm64 | vaultspec-core-v0.3.7-aarch64-unknown-linux-gnu.tar.gz |
| Windows · x86_64 | vaultspec-core-v0.3.7-x86_64-pc-windows-msvc.zip |
Version 0.3.7, published with checksums. Each download is an archive: extract it, then run the vaultspec-core inside. See direct downloads.
Install uv for the generated agent launchers, including when you acquire Core through pip or a binary. Use the command prefix that matches your installation.
Run vaultspec-core install from your repository root to create the vault and configure your agents. This provisions the repository; it does not install or upgrade the package. After upgrading the package, run vaultspec-core install --upgrade to refresh repository resources. For existing projects, follow the guides to join a project or upgrade Core. Environment settings and API keys have their own guide.
Search runs as a local service. You can use the harness without it.
The models need an NVIDIA GPU with CUDA on Linux or Windows, or Apple silicon. One host installation runs the service for the whole machine; a client added to a project installs no GPU packages and uses that service.
From PyPI, with uv
Installs the command on your PATH for repeated use.
uv tool install --python 3.13 "vaultspec-rag[gpu,mcp]" --index https://download.pytorch.org/whl/cu130 --index-strategy unsafe-first-matchThe default host installation: one service for every repository on this machine. On Apple silicon macOS, leave out the two --index options. To run the service from one project's own environment instead, follow the project dependency steps.
With Homebrew, on macOS and Linux
brew install nevenincs/tap/vaultspec-ragApple silicon macOS, and x86_64 and arm64 Linux with glibc 2.39 or newer.
With Scoop, on Windows
scoop bucket add nevenincs https://github.com/nevenincs/homebrew-tapscoop install nevenincs/vaultspec-ragStandalone binaries, no Python installation needed
| Platform | vaultspec-rag |
|---|---|
| macOS · Apple silicon | vaultspec-rag-v0.6.0-aarch64-apple-darwin.tar.gz |
| Linux · x86_64 | vaultspec-rag-v0.6.0-x86_64-unknown-linux-gnu.tar.gz |
| Linux · arm64 | vaultspec-rag-v0.6.0-aarch64-unknown-linux-gnu.tar.gz |
| Windows · x86_64 | vaultspec-rag-v0.6.0-x86_64-pc-windows-msvc.zip |
Version 0.6.0, published with checksums. Each download is an archive: extract it, then run the vaultspec-rag inside. The Linux archives need glibc 2.39 or newer; on older distributions use a Python route.
Install uv for the generated MCP launcher, including when you acquire RAG through Homebrew, Scoop or a binary. After installing the host with any channel above, run this from each repository root to configure its rules, skills and agent connections. The host needs a supported GPU and downloads its models and Qdrant when provisioning.
vaultspec-rag install --no-torch-configThen start one service for this user on this machine. The service shares the host environment across repositories. Set service environment variables before starting it; exported settings take precedence over saved settings.
vaultspec-rag server startFor a binary, run the extracted executable using its path or add it to your PATH. See the setup guide, upgrade sequence and environment settings guide. Package upgrades and install --upgrade are separate steps: stop the service, upgrade the host and matching clients, refresh each repository, then start the service once.
After installation, start a feature with your coding agent.