401 - Prompts are the new SOPs

The 300 series taught the mechanics of the prompt object: the fields, the arguments, the scopes, and what re-running one does. This series assumes that and asks a different question. Not how does a prompt work, but when is the right thing to make, and how does a team run on prompts the way it runs on written procedures.

During that hour, a good agent was doing more than answering. When you told it that the spring storms closed specific stores, that is the kind of correction a Plexara agent captures as an insight for an administrator to review and, if it holds, promote into the catalog. When you told it your team counts revenue net of next-period returns, that becomes durable knowledge every future session inherits. This is real, and it is covered in the 200 series. It is also not the thing you are missing three weeks later.

What you are missing is the procedure: the particular sequence of pulls, comparisons, annotations, and presentation choices that turned a blank prompt into a board-ready report. That is not a fact about your business. It is a way of doing one job. It deserves its own home, and it has one.

It is tempting to think the report was the output and the conversation was just the means. The opposite is closer to true. The report is a snapshot of one period. The conversation, specifically the corrections you made on each pass, is the reusable part. Look at what the final version actually encoded.

Every operations team that survives a key person leaving has learned the same lesson: the way a job is done has to live somewhere other than one person’s head. The standard operating procedure is the artifact that holds it. It is boring on purpose. It is the steps, in order, with the gotchas called out, so the next person produces the same quality without rediscovering the path.

A saved prompt is that artifact for work you do with the agent. The report you went back and forth on was a procedure being discovered in real time. Saving it as a prompt is writing the procedure down. The difference between a team that does this and one that does not is the difference between starting next month’s report from the version that already works and starting it from a blank prompt and a fading memory.

The discipline cuts both ways. A one-off question you will never ask again is not a procedure, and saving it as a prompt just clutters the list everyone scans. A genuinely new business fact you discovered is knowledge, and filing it as a step inside one report buries it where the next report cannot find it. The test is simple: will you, or someone on your team, want to run this same shape of job again with different inputs. If yes, it is a procedure, and it is a prompt. If it is a fact that should change how every job runs, it is knowledge, and it belongs in memory or an insight.

The report from the opening is a clean yes. You will want the year-over-year, holiday-annotated, closure-marked sales view again, for the next period and probably for a different region. The shape is stable; the inputs change. That is the exact signature of something worth saving as a prompt.

There is one more reason teams skip this step: writing a good prompt by hand, after the fact, is its own chore. You would be reconstructing an hour of decisions from memory. The next article removes that chore entirely.

Four terms anchor the series. The first two are the distinction this article is built on; the last two are the analogy it runs on.