---
id: "action-invest-in-spec-writing"
type: "action-item"
source_timestamps: ["00:20:00"]
tags: ["skills-development", "systems-design"]
related: ["concept-spec-quality-bottleneck"]
action: "Train engineers to write hyper-precise, comprehensive system specifications."
outcome: "Overcome the new bottleneck of AI development and ensure accurate implementations."
sources: ["s01-5-levels-ai-coding"]
sourceVaultSlug: "s01-5-levels-ai-coding"
originDay: 1
---
# Invest in Specification Writing

## Directive
Train engineers to shift their focus **from writing syntax to writing hyper-precise, comprehensive specifications**. The primary bottleneck is no longer implementation speed — it is the clarity of instructions given to the AI. See [[concept-spec-quality-bottleneck]].

## Specific Steps
1. Establish a spec-authoring style guide covering: edge cases, security models, architectural constraints, integration boundaries, observable behaviors.
2. Treat specs as first-class versioned artifacts — review them with the same rigor previously reserved for code.
3. Invest in spec-review as a *senior* discipline. Senior engineers no longer review code; they review specs (Level 4) or only outcomes (Level 5).
4. Use specs as the input contract to your scenario tests (see [[action-implement-scenario-testing]]).
5. Hire and promote based on spec-writing ability — a discipline closer to legal drafting than to syntax.

## Expected Outcome
The agent builds the right thing; ambiguity is squeezed out of the development pipeline.