How do you govern and version Prompt Templates across a development lifecycle?

Prompt Template governance is critical because changes to a template directly affect agent behaviour and quality. Best practices:

1. Versioning: Salesforce stores Prompt Template versions natively — each save creates a new version. Only one version is active at a time. Review version history to understand how a template evolved and roll back if a change degrades output quality.
2. Source control: Retrieve template metadata using Salesforce CLI and store it in a Git repository. This enables peer review of prompt changes via pull requests, the same as code changes.
3. Test cases: Maintain a documented set of representative inputs and expected outputs for each template. Run these test cases against new template versions in a sandbox before promoting to production.
4. Staging environment testing: Always test prompt changes in a sandbox or scratch org with real representative data before deploying. LLM outputs are non-deterministic — test multiple times with the same input to assess consistency.
5. Separation of concerns: Keep templates focused on a single responsibility. A template that both retrieves data and formats an email response is harder to maintain than two templates with clear boundaries.
6. Documentation: Add inline comments in the template (where the template engine supports it) describing the intent, expected inputs, and the grounding data source — making templates self-documenting for the next maintainer.