PromptOps
Synonyms: prompt management, prompt versioning, LLMOps, prompt lifecycle management
Definition
Use cases
- The Friday tone fix: A PM softens the support bot's tone. By Monday it promises refunds the policy doesn't allow, and nobody knows which version is live.
- Prompt stuck in code: A UX writer wants to fix one awkward phrase. It sits in a code file, so the fix waits 2 sprints for an engineer.
- The model swap: The team upgrades the model. The same prompt now writes longer answers that overflow the UI card.
How it's used in practice
- Move prompts into a registry: Versions, diffs, and staging or production labels, editable without a code deploy.
- Build a golden set: A few dozen real user inputs with expected behavior, run on every change.
- Review prompt diffs as copy: A designer and an engineer both sign off.
- Release with labels: Roll back by moving the production label to the last good version.
- Log the version with every response: Support tickets then trace straight to the prompt that caused them.
Challenges & limitations
- Evals cost real time: Someone has to label examples and keep them current.
- Model updates break tuned prompts: A prompt tuned for one model can drift on the next.
- Vendor lock-in: OpenAI now tells new projects not to create reusable prompt objects, which it is deprecating. Keep prompts portable.
Free resources
- Langfuse: Prompt version control — version IDs, production and staging labels, and rollback by moving a label.
- Hamel Husain: Your AI Product Needs Evals — the 3 levels of evaluation, shown on a real estate AI assistant.
- OpenAI: Prompting guide — prompt guidance, plus OpenAI's note that reusable prompt objects are being deprecated.
