Docs/Integrations/Integrations

Integrations

Integrations are optional tools you can turn on at scaffold time with --integrations, or add later with spec-init customize --add. Each is opt-in, free/open-source, and layered in without touching your source code.

Add at scaffold time (spec-init init my-app --integrations graphify,caveman) or later (spec-init customize --add obsidian). Remove any with customize --remove <name>.

The catalog

Graphify

Query the codebase as a knowledge graph instead of full-repo greps.

Obsidian

Navigate the claude/ and design/ markdown as a linked graph vault.

Caveman

Ultra-compressed replies cut output tokens ~65% while keeping code byte-exact.

agentmemory

Persistent cross-session memory injected back at session start.

openwiki

Auto-generates an agent-facing documentation wiki for the codebase.

ponytail

A minimalism ruleset: the agent writes the least code necessary.

Open Code Review

AI code-review CLI (ocr) for line-level findings on diffs, in CI or pre-push.

How integrations work

Each integration is a per-integration file tree plus marked-up blocks in CLAUDE.md and README. Turning one on copies its files and keeps its blocks; turning it off removes both, leaving zero residual files. Your active integrations are recorded in spec.config.js (the ground-truth config), so upgrade and customize always know what is on.

Local install + docs

When you enable an integration that ships a one-line installer (e.g. Caveman), the CLI runs it for you and prints each integration’s official docs link in the terminal. Pass --no-install to skip the auto-install and just get the commands + links. Follow the docs link above for setup and usage of each tool.

Most of these tools reuse your existing coding-agent model (or offer a local, zero-cost path), so you rarely need a separate paid API key.