Spec
Spesifikasi
A written description of what to build, written before building it.
A spec is the written statement of what the work is: the goal, the constraints, the shape of the output, and what counts as done. Writing one is the cheapest way to find out that the request was ambiguous, because the gaps become visible when you have to put them in words.
For AI-assisted work the spec matters more, not less. The model will build something reasonable from an ambiguous request, and the ambiguity then gets resolved by whatever the code happened to do, silently. A spec moves those decisions to where a person can still change them.
A good spec is short enough to read and specific enough to disagree with. If nobody can point at a line and say "this is wrong", the spec is not specific enough to be useful.
Related terms
Context Engineering
Deciding what goes into the model's context, and what stays out.
Ticket
A unit of work small enough to be scoped, done, and checked.
Human in the Loop
A person who reviews, approves, or corrects the agent's work at key points.
Vibe Coding
Writing software by describing what you want and accepting the result without reading it closely.
Handoff
Moving work from one session, or one agent, to another without losing the thread.
Want this working inside your team?
It starts with one conversation about your workflow.