SPEED-BOK v1.4.7

Spec Engineering

Producing specifications at every tier with quality.

Specifications are easy to write badly and hard to write well. Spec Engineering is the discipline of writing well rather than merely writing — and it begins with the User Tell, where the user's need enters the program.

Start here

Core tasks

Tell authorship

Draft User Tells with every slot filled concretely — reviewed and locked before any feature spec is derived.

Scoping

Identify which tier a specification belongs at, and what portion of the program it governs.

Drafting

Write the specification in a form that matches the tier's conventions.

Linking

Attach the specification to its upstream authority and to the lower-tier artifacts that implement it.

Validation framing

Specify how conformance will be checked — mechanically, or by defined review criteria.

Lifecycle stewardship

Move the specification through its states from Drafted to Locked, with review at each boundary.

From knowing to running

Knowing SPEED and running it are two different things. When you're ready to practice the methodology inside a program that runs it, the implementor path is where you begin.

Begin the implementor path