Prompt versioning is a deployment problem, not a document problem

Ask any team who has shipped an agent which prompt is running in production right now. The honest answer is usually a pause, followed by someone opening a document.

Why documents lose

A prompt in a doc has no version, no reviewer, no rollback and no link to the traces it produced. When quality drops you cannot answer the only question that matters: what changed?

Moving prompts into your repository fixes the audit trail but creates a new problem — every copy edit now needs a deploy, so non-engineers stop suggesting improvements and the prompt goes stale.

Config, with review

The middle path is to treat prompts as versioned configuration: edited outside the deploy cycle, but diffed, reviewed and attached to every trace they generate. Rolling back becomes a click, and any regression can be traced to the exact revision that caused it.

The side effect nobody expects is cultural. When a prompt change is reviewable, people start reviewing them.