Plexara
Learning / Prompts as SOPs
Prompts as SOPs
401 - Prompts are the new SOPs
You work with the agent for an hour to get one report exactly right, with a year-over-year cut, holiday annotations, and storm-closure markers. The agent saves durable business knowledge on its own. But that specialized report is not institutional knowledge, it is a procedure. This article draws the line between the two, and makes the case that a saved prompt is the standard operating procedure for an AI-run job.
402 - Letting the agent write the prompt
The cheapest way to save a procedure is to not write it yourself. The agent that just spent an hour producing your report still holds the tool order, the corrections, and the values worth turning into arguments. Ask it to author the prompt, review the draft, and save it. This article covers the move, why the agent is the better author, and how to read what it produces.
403 - Sharing prompts, and closing the loop with feedback
A procedure is only worth as much as the people who can run it. Plexara distributes a prompt two ways: a direct share to one teammate, or a promotion to a whole role or company through the admin review queue. A shared prompt is live, not a copy. Feedback threads then carry corrections back, with a validation step and a path into the knowledge catalog, and the deprecate-and-supersede lifecycle retires old versions cleanly.
404 - Running prompts, by hand and on a schedule
A saved prompt runs two ways: at your keyboard when you want the report now, and on a schedule when you want it to arrive on a cadence. Running by hand takes a sentence: name it to the agent under any handle it knows, pick it in the List Prompts app, or paste the portal’s copyable invocation. Scheduling is not a Plexara feature at all; it lives in your agent, from an in-session loop to a cloud routine that runs when your machine is off. This article covers both, where the output goes, and how a share turns an unattended run into email somebody actually reads.