spec-sync docs
Documentation
spec-sync docs
Bidirectional spec-to-code validation. Written in Rust, single binary, 12 languages. Everything from a 5-minute quickstart to the full CLI surface, configuration, and CI integrations.
Getting started
Spec format
Reference
CLI reference
Every spec-sync command, flag, exit code, and JSON output shape.
Configuration
Canonical validation configuration and the versioned verified-SDD policy.
Workflow guide
The verified delivery lifecycle from deterministic interview through acceptance and archival.
Cross-project references
Validate spec dependencies across repositories with the owner/repo@module syntax.
Architecture
How spec-sync is built: source layout, validation pipeline, adding a language.
Integrations
Comparisons
Spec Kit comparison
Compare deterministic contract enforcement with an extensible agent-led SDD toolkit.
OpenSpec comparison
Compare two brownfield SDD lifecycles and their enforcement boundaries.
Using SDD tools together
Assign durable ownership when SpecSync, Spec Kit, and OpenSpec share a repository.
Adversarial SDD proof
Executable evidence for approvals, drift detection, change coverage, and verification binding.
Examples
All examples →Worked, end-to-end walkthroughs.
Sync a Rust workspace end-to-end
From spec-sync check to a tagged release, with cross-crate references.
8 steps · ~12 min
PolyglotMulti-language repo: TS + Python + Rust
One spec format, three languages, one CI gate.
7 steps · ~10 min
CI / CDCI gate with the GitHub Action
Block merges when specs drift from code.
5 steps · ~7 min