---
id: "concept-specification-engineering"
type: "concept"
source_timestamps: ["00:02:38", "00:03:10"]
tags: ["prompt-engineering", "skill-development"]
related: ["framework-ai-skill-hierarchy", "concept-context-engineering"]
definition: "The apex AI skill of precisely defining constraints, goals, and context for an AI, which relies heavily on automated memory systems to avoid manual context-transfer."
sources: ["s22-saas-replacement"]
sourceVaultSlug: "s22-saas-replacement"
originDay: 22
---
# Specification Engineering

## Definition

The apex AI skill of precisely defining constraints, goals, and context for an AI, which relies heavily on automated memory systems to avoid manual context-transfer.

## Position in the Hierarchy

Specification Engineering sits at the top of [[framework-ai-skill-hierarchy]], above Prompt Craft, Context Engineering, and Intent Engineering. The speaker's argument: the bottleneck on AI output quality is no longer the model's reasoning — it is the human's ability to **fully specify** the problem, including constraints, prior decisions, and project history.

## The Memory Dependency

Humans are bad at remembering and re-typing exhaustive specs every interaction. Therefore, real Specification Engineering depends on an automated memory layer (a [[concept-open-brain-d22]]) that quietly injects the necessary background. The user then only needs to specify **the delta** — the new decision or new problem — while the system handles the rest.

See [[quote-best-prompt-cannot-compensate]] for the speaker's blunt framing: no amount of clever prompting compensates for an AI that does not know what you've been working on.

## Implication

If you want to live at this apex skill tier, you must invest in infrastructure (memory) before you invest in prompt cleverness. This is the same priority inversion captured in [[claim-architecture-over-models]] and [[contrarian-architecture-over-models]].


## Related across days
- [[concept-spec-quality-bottleneck]]
- [[concept-intent-engineering]]
- [[concept-spec-driven-development]]
- [[concept-specification-vs-execution]]