Comparison and limits

The family's overview compares it with eleven projects nearby. Each statement there about another project was read from that project's own repository, documentation or registry entry on 2026-11-09, and links to where it was read. Those projects change every week, so this page does not repeat what the overview says of them: it names them, and says what the spec family does in each area. Read the overview, and follow its links, before relying on a comparison.

Neighbours

AreaProjectsWhat the spec family does there
Spec-driven developmentSpec Kit, OpenSpecKeeps a specification true after it is written, deterministically, on every change. spec-graph reads the layouts Spec Kit, OpenSpec and Kiro write with no configuration (layouts).
ADR enforcementArchgate, Mneme, adrkitA spec-guard rule is an HTML comment under the sentence it enforces, in the ADR itself, and is not run once the ADR is superseded (document status); spec-graph holds the ADRs' lifecycle. An exception to a protected file counts only as a commit signed by a key the base branch's allowed signers list (rulings).
Documentation checksDocGuard, ctxgrdAn Implemented claim needs a directive that counts a test by its name, which spec-guard prove shows can fail (claims); a ticked box needs a commit git holds (checklists). The code is held to the documents, as well as the documents to each other.
Scoped agent workTrailbun, spec-gatesA round of agent work runs under a brief, a Markdown file a person approves; each brief protects its own files for its own round, and a protected path opens only by a ruling the person signs (rulings).
Import rulesdependency-cruiser, import-linterspec-guard's import rules are written in the ADR under the sentence they enforce, in JavaScript and TypeScript, Python, Go, Rust and C#, and stop being enforced when the ADR is superseded (imports). The two kinds of tool run side by side.

What the tools do not do

The overview's full list gives the reason for each and where it is decided.