Spec-driven development: agents and people read from one source

In SimaCMS every capability has a formal spec: 65 of them, saying what the system does rather than how. Every behaviour decision goes through OpenSpec as well: proposal, design, tasks and, at the end, archive.

Why

An agent starts from zero every time. If the system’s behaviour lives only in people’s heads, the agent guesses it; if it lives in a spec, the agent reads it. The same holds for a new teammate.

One simple rule

When code and document disagree, the code is the truth and the document is fixed that day. A change that alters behaviour updates its spec in the same PR.