Home/
Part XIV — Team Workflows and "Shipping With Adults in the Room"/43. Collaboration Patterns/43.3 "Spec → prompt → eval → ship" as a team pipeline
43.3 "Spec → prompt → eval → ship" as a team pipeline
Overview and links for this section of the guide.
On this page
The Pipeline
Stop "vibing" in production. 1. Spec: "We need to summarize emails." 2. Prompt: Engineer writes V1. 3. Eval: Run V1 against 50 test emails. Score: 80%. 4. Refine: Engineer tweaks prompt. Score: 95%. 5. Ship: Deploy V2.
The Spec
The spec must define "Success." - "The summary must capture the deadline." - "The summary must be under 50 words." - "The summary must not mention the sender's name."