‹ All projects
DesignLLM flows

Prompt release pipeline

Prompts treated like code: versioned, reviewed, rolled out slowly, and rolled back in one step.

The problem

Prompts lived in string literals. A one-word edit shipped with no review and no way back.

How it works

  1. 01Write
  2. 02Review diff
  3. 03Run evals
  4. 04Staged rollout
  5. 05Rollback

What was hard

  • A prompt change cannot merge until the eval suite passes.
  • Every answer in production records the exact prompt version that made it.

The goal

Rolling back a bad prompt becomes a normal deploy.

This is a design I worked out on paper — the problem, the approach and the trade-offs. It is not a shipped product.

Built with

VersioningEvals in CIFeature flags