← sources

Draft policy: treat edits to a prompt that feeds a system like any other change. What would you add or cut?

source: reddit (reddit:PromptEngineering)published 2026-10-19 01:21ingested 2026-10-20 02:39

retained text

I’ve been thinking about prompts that no longer just produce text for a person to read, but feed something else: a script that parses the answer and routes tickets, a workflow that fills a field, an automation that decides who gets an email.

The moment something depends on that output, editing the prompt is a change to the system, even though it looks like editing a paragraph. And it usually skips everything a code change goes through: no review, no tests, often no record of who changed it or why.

Here’s a rough draft of a policy for it. Three rules, deliberately small:

1. **Anything that feeds a system has an owner and a written contract.** One person is responsible, and the expected output (fields, allowed values, what happens when data is missing) is written down somewhere other than the prompt itself.
2. **Edits are tested against a fixed set of inputs before they go live.** Including a few awkward ones: empty fields, very long text, odd formatting. The set is short enough that someone will actually run it.
3. **Every change gets a one-line reason and a name.** So when routing starts going wrong three weeks later, you can see what changed and when.

What this wouldn’t cover, and I should say so up front:

* a prompt that only drafts something a human reads before sending doesn’t need any of it
* a well-formed output can still be wrong, so passing the contract isn’t the same as being right
* a fixed set of test inputs only catches the cases someone thought of

The part I’m least sure about is the threshold. Too low and people ignore the policy because it covers every scribbled prompt. Too high and the one that matters slips through. The signs I’d use are: something parses the output, someone other than the author edits or runs it, or a wrong output has real consequences.

So, for people who run change management: would you add something here, cut something, or put the line somewhere else? And does your current process have any hook for this, or do prompts live outside it entirely?

I wrote about the reasoning behind this in more detail, in case it’s useful: [https://medium.com/@nagatomopedro05/a-prompt-becomes-an-api-the-day-something-depends-on-it-06a30572a4ed](https://medium.com/@nagatomopedro05/a-prompt-becomes-an-api-the-day-something-depends-on-it-06a30572a4ed)

document fetched 2026-10-20 00:39 · canonical https://reddit.com/r/PromptEngineering/comments/1x9jvpq/draft_policy_treat_edits_to_a_prompt_that_feeds_a