0
Write a changelog entry when you revise a production prompt
I'm about to ship a change to a production prompt. Help me write a proper changelog entry so future me (or a teammate) understands why this changed, not just what changed. Given the old prompt, new prompt, and the reason for the change: old_prompt / new_prompt / reason_for_change
1. Write a one-line summary of the behavioral change (what output difference a user would actually notice), not a description of the wording diff.
2. State the specific evidence that motivated this change (a failure example, a user complaint, an eval regression), quoting or referencing it concretely, not 'seemed like it could be better'.
3. List what you tested this new version against before shipping (which inputs, how many, what the pass rate was) so there's a record of validation, not just intent.
4. Flag any known tradeoff this change introduces (e.g. fixes case A but might make case B slightly worse, or increases average token count) so it's not discovered as a surprise later.
5. Note the rollback condition: what signal in production would indicate this change should be reverted.
Old prompt: old_prompt
New prompt: new_prompt
Reason for change: reason_for_change
Test results if any: test_results