We are updating our core processes using the EOS Three Step Process. How do we document an AI-assisted workflow so that anyone on the team can execute it consistently without getting confused by technical prompts?

Question

Tyler Smith · Accepted Answer

When documenting your core processes using the EOS Three Step Process, your goal is to keep things simple and high-level. Do not clutter your SOPs with long, technical prompt strings that might change next month.

First, document the workflow at a high level. Identify the clear trigger, the input needed, the AI step, the human verification step, and the final output. This keeps the document highly readable and easy to follow.

Second, separate the specific prompts from the main process document. Create a central, accessible library or template folder for your approved AI prompts. In your main process document, simply reference the specific prompt ID or link to the template. For example, write, Use prompt template alpha to generate the draft. This allows you to update and optimize your prompts in one central place without having to rewrite your entire core process manual every time you refine a prompt.

Third, place heavy emphasis on the human validation step. Clearly define what the human must check before the work moves to the next stage. What are the common errors to look for? What is the standard for quality?

By keeping your documentation clean and focused on the human-in-the-loop validation, you ensure your processes remain simple to teach, simple to learn, and simple to manage.