# spec family > Four deterministic command-line tools, each one npm package with no runtime dependencies, that hold a repository's code, and the coding agents that write it, to what its Markdown says: specifications, ADRs, checklists, registers, agent instructions and the briefs agents work under. The tools are spec-brief, spec-graph, spec-guard and spec-harness, published on npm under the `@spec-family` scope; the unscoped names are not these packages. Install one with `npm install --save-dev @spec-family/` and run it with `npx --no-install @spec-family/`. They need Node 22 or later, call no model and make no network request. Exit codes: `0` clean, `1` found something, `2` the result cannot be trusted. Each page below is the Markdown version of a page of this site. Every command's output on them is printed by spec-brief 0.15.0, spec-graph 0.26.0, spec-guard 0.35.0 and spec-harness 0.26.0 in the site's CI, on the example repository at commit 77b504f. ## Pages - [spec family](https://spec-family.github.io/index.md): Four command-line tools that hold your code, and the agents that write it, to what your Markdown says: deterministic, with no runtime dependencies. - [Which document do you want to keep true?](https://spec-family.github.io/documents/index.md): Eight kinds of Markdown document, what goes wrong in each, the spec-family tool that holds it, and the rules and commands that do. - [Two stories](https://spec-family.github.io/stories/index.md): Two stories from the spec-family example repository, an agent's write refused and a claim with nothing behind it, with what the tools printed. - [A write refused](https://spec-family.github.io/stories/write-refused/index.md): An agent's write to a file its brief protects is refused before it is made; its write through the shell is not, and spec-harness audit finds it. - [A claim without evidence](https://spec-family.github.io/stories/claim-without-evidence/index.md): A specification marked Implemented with no test, a roadmap item ticked for a commit never made, and agent instructions naming a missing file: spec-guard and spec-graph turn CI red on each. - [The four tools](https://spec-family.github.io/tools/index.md): spec-brief, spec-graph, spec-guard and spec-harness, each with one command run on the example repository and what the pinned release printed. - [Comparison and limits](https://spec-family.github.io/compare/index.md): Where the spec family stands among spec-driven development, ADR enforcement, documentation checks, scoped agent work and import rules, and what its tools do not do. ## Reference - [spec-brief 0.15.0 reference](https://raw.githubusercontent.com/spec-family/spec-brief/v0.15.0/docs/reference/README.md): every command, rule, option and key of the release this site pins. - [spec-graph 0.26.0 reference](https://raw.githubusercontent.com/spec-family/spec-graph/v0.26.0/docs/reference/README.md): every command, rule, option and key of the release this site pins. - [spec-guard 0.35.0 reference](https://raw.githubusercontent.com/spec-family/spec-guard/v0.35.0/docs/reference/README.md): every command, rule, option and key of the release this site pins. - [spec-harness 0.26.0 reference](https://raw.githubusercontent.com/spec-family/spec-harness/v0.26.0/docs/reference/README.md): every command, rule, option and key of the release this site pins. - [Overview](https://raw.githubusercontent.com/spec-family/spec-core/main/docs/overview.md): the family's positioning, the eight kinds of document, its neighbours and what the tools do not do. - [Example repository README](https://raw.githubusercontent.com/spec-family/example/77b504ff1625988557b2767356b68d4a40f09a8c/README.md): the two stories as the example tells them. ## Optional - [spec-brief 0.15.0 README](https://raw.githubusercontent.com/spec-family/spec-brief/v0.15.0/README.md): Lifecycle management for task briefs: lint the contract, map parallel collisions, and archive a round in one atomic command. - [spec-graph 0.26.0 README](https://raw.githubusercontent.com/spec-family/spec-graph/v0.26.0/README.md): Turn Markdown specs into a verifiable relational graph. Catches ghost handovers, stale premises, broken references, work marked done without its evidence, and commits and paths that are not there, in CI. - [spec-guard 0.35.0 README](https://raw.githubusercontent.com/spec-family/spec-guard/v0.35.0/README.md): Hold your code to what your Markdown says about it: the claims specs, ADRs, READMEs and agent instructions make about your codebase, as assertions that run in CI. - [spec-harness 0.26.0 README](https://raw.githubusercontent.com/spec-family/spec-harness/v0.26.0/README.md): The agent-facing member of the spec-* tools: context for a round, a guard on the agent's writes, an audit when it ends, probes that prove a defect before it is filed, and rulings a person signs. - [Concepts](https://raw.githubusercontent.com/spec-family/spec-core/main/docs/concepts.md): every word the tools share, in a sentence or two. - [Adopting](https://raw.githubusercontent.com/spec-family/spec-core/main/docs/adopting.md): from one tool to the whole loop, CI, and the forge settings for a repository where agents write most of the code. - [Tutorial](https://raw.githubusercontent.com/spec-family/spec-core/main/docs/tutorial.md): one round of agent work from the brief to the archive.