Documentation
The CLI & MCP server
The Specline CLI checks your repo. It reads your markdown, your YAML, your folder structure — never your code, never a model, never the network — and answers one question the same way every time: does this repo have the right shape? Same input, same answer, every run.
One engine, one output contract. It runs three ways:
Getting started →
Set up a new repo, or convert an existing one's docs to Specline.
Install →
Get the
specline command on your machine. Node 22+, no build step.CLI →
specline check, rules, spec — flags, modes, exit codes.MCP server →
Wire Specline in as a tool an agent calls while it plans with you.
Rule catalog →
Every
rule_id, its severity, scope, tier, and downgradable flag.Agent setup →
The
CLAUDE.md brief that makes an agent aware of Specline.The orchestrator →
The pluggable runner that drives a ratified spec autonomously — Specline defines the contract, not the runner.
Why now →
Why Specline helps more as models get stronger.
Raw canon ↗
The full methodology as markdown — what Specline enforces, for your agents.
▲
Specline checks the shape, nothing more. It never judges meaning — sizing, tense, whether the spec is right. That stays yours, at the two gates.