---
id: "quote-spec-becomes-eval"
type: "quote"
source_timestamps: ["00:10:56", "00:11:02"]
tags: ["best-practices", "testing"]
related: ["concept-spec-driven-development", "action-write-specs-first", "prereq-evals"]
speakers: ["Nate B. Jones"]
speaker: "Nate B. Jones"
sources: ["s23-amazon-16k-engineers"]
sourceVaultSlug: "s23-amazon-16k-engineers"
originDay: 23
---
# The Spec Becomes the Eval

## Quote

> *"The spec becomes the eval. It's actually not that hard. If you can write out a clear spec, that is how you get an eval that you can then set the agent against."*

— **Nate B. Jones** (see [[entity-nate-b-jones]]), 00:10:56

## Why It Matters

This quote is the operational core of [[concept-spec-driven-development]] and the action [[action-write-specs-first]]. It collapses two artifacts that engineering teams typically treat as separate (specifications and evaluation suites) into one — and uses the collapse to force human comprehension upstream of AI generation.

## Adjacent Validation

The enrichment overlay highlights that this principle is functionally identical to Stanford HAI's recommendation that capability claims must match what is actually tested — see [[entity-org-stanford-hai]]. The 'spec becomes eval' move ensures the AI's tested capability and the team's claimed capability are the same artifact.

## Prerequisite

Readers unfamiliar with AI evals should review [[prereq-evals]] first.