Spec / PRD-driven development
Humans write specs; agents write the implementation. The spec becomes the contract.
In one sentence
The specification (spec, PRD) is the source artifact; code, tests, and docs are derived from it. In a Cognitive Enterprise, humans write specs and agents write the implementation: the spec becomes the contract.
Before
Request in conversation
What it does
Spec as contract
After
Code, tests, and docs derived from it
Example
The correspondence spec defines: input (report and history), output (letter), acceptance criteria (the five eval criteria), and what gets escalated to a human. From it, the agent writes the prompt, script, tests, and documentation.
When someone wants to change the behavior, they change the spec instead of hunting for an adjective in the prompt.
In practice
- One spec per process, with measurable acceptance criteria.
- Behavior changed? Change the spec first, the prompt second.
- Without acceptance criteria, the spec is just expressing a wish.
How to make it tangible
One document per process: input, output, acceptance criteria, and what gets escalated. Everything derives from it.
Connects with
Translated from Portuguese with AI assistance.