Find the facts that belong to one run
When you build a workflow around one real case, that case’s details slip in: a customer’s name, a deadline, a file name, the people to send to or an exception you needed once. Those lines make the workflow quietly wrong for the next case, and the agent may carry them into it. They belong in your Context Sandwich, the Task, Context, Constraints and Output Check you write for each run.
Some specific lines can stay because they’re true every run: your name or role in the workflow’s title, a role such as “my manager”, an audience that never changes, a fixed rhythm such as “every Friday”, your success measure’s starting point and the name of its log, or the name of one of your Workflow Cards.
Start a new chat, attach your workflow and send the prompt. Then read your file yourself for any it missed, such as the customer, dates and people from the case you built it around.
My Business Results Workflow is attached or pasted below. It should hold only what stays the same every time it runs. Help me find anything that belongs to one run. Do not change the file. 1. Quote every line that names a specific person, customer, project, place, date, deadline, number, file, recipient or one-time exception, word for word, with the section it's in. 2. For each, say whether it reads as true every time the workflow runs, such as a role, my name or role in the workflow's title, an audience that never changes, a fixed schedule, my success measure's starting point, the name of its log or the name of one of my Workflow Cards, or true for one run only. 3. For each one-run fact, suggest general wording the workflow could use instead, such as "the customer named in this run's source", or say "move to the Context Sandwich" or "delete". Use only what my workflow says. If you find nothing, say so. [paste your Business Results Workflow here if it isn't attached]
Decide where each fact goes
For each one-run fact, choose one of these:
- General wording in the workflow, when the workflow needs the idea every run and not the detail, such as “the customer named in this run’s source” in place of the customer’s name.
- Your Context Sandwich, when the detail matters for one run only: a deadline, the people to update this time or a one-time exception.
- Another file, when it’s true every run but isn’t about this workflow, such as your role, which belongs in your Agent Profile.
- Delete, when it’s out of date and no run needs it.
Note your decision beside each quote.
Make the changes and save
Open your workflow in your plain-text editor and make each change you noted: write the general wording, take out the facts that move to your Context Sandwich or another file, and delete what’s out of date. Keep the facts you moved in a short note outside the folder you keep your workflow in, so you can put them in your next Context Sandwich if they still apply, and delete it once you don’t need them.
Read the whole workflow once more with the case you built it around in mind. Then save the file in place of the old one in My Agent Files, or another folder you’ll find again. If you’ve added your workflow to your AI tool, such as a skill or a Notebook’s References, replace that copy too. If you moved a line into another file, such as your Agent Profile, save that file too.
Write a lean Context Sandwich for the next run
With one run’s facts out of the workflow, each run’s Context Sandwich carries them, and only them. The rule from Session 4 still holds: if it stays the same every time, make it reusable. If it changes this time, keep it current. For your next run:
- Task: run your workflow by name, plus anything different this time, such as a second version for another reader.
- Context: this run’s permitted facts, source, dates and who’s involved.
- Constraints: “Use the workflow defaults,” plus a one-time limit or exception only if this run has one.
- Output Check: “Use the workflow defaults,” plus a one-time addition only if this run needs one.
If nothing changed in Constraints or Output Check, “Use the workflow defaults” is the whole line. Run my Business Results Workflow, in step 5, has these four parts with the defaults already written, so you fill in only what’s new.
Run a second case and check for leftovers
Now run the workflow on a second case of the same work, different from the one you built it around, prepared the way the data rules say, or a short made-up one. The process stays and the content changes. Before you send it, predict what should stay the same: the steps, their order, the standard, the shape of the output and your stops. The facts, dates, source, risks and decisions should all be new.
Start a new chat, attach your updated workflow and its files, and send Run my Business Results Workflow with your lean Context Sandwich and your second case.
Run my Business Results WorkflowUse the files I have attached or pasted below for this conversation. My Business Results Workflow says what this work should accomplish, which of my other files and Workflow Cards to use, where to stop for my review and what to return. If my Business Results Workflow is missing, ask me for it before you start. Continue without any other file I've marked "not provided". MY FILES [paste the text of your Business Results Workflow, the Workflow Cards it names, your Safety & Security Rules, Agent Profile and Communication Style Guide here, or attach the files and write their names here. Write "not provided" for a file you don't have yet.] TASK Run my [name of your Business Results Workflow] using the source below. [add anything different about this run, or delete this line] CONTEXT [what this run covers, such as which meeting or reporting period, and anything that changed this time] CONSTRAINTS Use the workflow defaults. [add a limit for this run only, such as a shorter message, or delete this line] OUTPUT CHECK Use the workflow defaults. [add anything extra this run needs, such as one more person to review, or delete this line] SOURCE [paste this run's prepared source here]
Check the result for anything from your first case: a name, date, recipient, number or exception that isn’t in this run’s source or Context Sandwich. Check that it didn’t fill a gap with an invented fact, and that it stopped at your checkpoints as usual.
If something carried over, find where it came from. A line still in your workflow sends you back to step 3. A file or notes from an earlier run attached to this chat, or still in a Project or Notebook, should be removed. If it’s in none of your files, tell the agent in the same chat to use only this run’s files and context. Fix it, then run again in a new chat.
Save a blank copy of your four Context Sandwich lines, with this run’s facts taken out and only “Use the workflow defaults” left, in My Agent Files, or another folder you’ll find again, and edit it to fit how you run this work. Fill in a fresh copy each run, and don’t attach an old one. The next time you change your workflow after a real run, read it once for that run’s facts before you save.
Confirm your result
Confirm the outcomes below to finish this guide.
Final checks
Your saved workflow holds no names, dates, files or exceptions from a single run, and each fact you moved out has a home in your Context Sandwich or another file.
A second case, run with a lean Context Sandwich, came back with only its own facts and nothing carried over from the first.
Provide Feedback
Thanks. That went straight to the people who write these guides.
Next in Week 5
Measure Whether Your Workflow Actually Helps
Continue in the suggested order, or choose another guide for your task.