Maintenance status: Spec Led Development and its tools are no longer maintained. These repositories remain public as a reference. No new features, bug fixes, or support are planned.
Spec 1.0: This page reflects the last published portable core release.Spec Led Development is language-agnostic. The tooling is not. That is an important distinction. The method should stay portable across languages. The commands and package names will vary by stack.
The method comes first
The core ideas do not depend on one runtime:- current truth in the repo
- a small authored model
- derived verification state
- a repeatable drift check
Elixir package
specled_ex is the most complete published implementation of the 1.0 portable core.
Its command story is intentionally simple:
mix spec.primefor session-start contextmix spec.init,mix spec.next, andmix spec.checkfor the default local loopmix spec.statusandmix spec.decision.newwhen you need coverage or durable ADR supportmix spec.indexandmix spec.validateas lower-level plumbing
specled_ex has the simplest beginner loop:
- run
mix spec.prime --base HEADwhen you enter the repo or hand work to an agent - make the change and tighten the smallest proof
- run
mix spec.next - update the subject or ADR if needed
- run
mix spec.check --base HEAD
CI support
The project also includes shared GitHub Actions support so repositories can run the same verification loop in CI that they run locally. That matters because Spec Led Development is not just a local authoring habit. It is supposed to create lasting back pressure when code changes without the matching intent and verification changes.Project repos
If you want the actual project repos, start here:Portable reference without tooling
The portable core can be read independently of the published tools. Its minimum repository contract is:.spec/specs/*.spec.md.spec/state.json- one local verification command