Specification work makes the implicit explicit — it transforms requirements, assumptions, or design intentions into written artifacts that can be verified against. In systems engineering, a specification precedes implementation and provides the standard against which qualification is performed.

Specify is preferred over docs because documentation can describe anything, including what already exists. Specification work is forward-looking: it defines what should be true before or alongside the work that makes it true.