You ask your agent for a weekly customer update. The first draft is close, but not quite right. Put the numbers first. Group the replies by country. Keep the closing sentence short.
After a few corrections, you have the version you wanted.
Next week, you open a new conversation. The task is familiar. So are the corrections.
The work got done, but the way of doing it stayed in last week's chat.
Keep the method, not the conversation#
A finished update is useful once. The decisions that made it good can be useful every week.
Those decisions belong in a playbook: a short account of how to do this particular task. Not a transcript. Not a collection of everything you've ever told an agent. Just the instructions that should survive the next conversation.
For that customer update, it might start with three lines:
- Lead with contact counts and response rate.
- Group replies by country.
- End with the next action, in one sentence.
The next run starts there. You still give the agent this week's numbers and tell it what changed. You don't have to explain the format again.
Let the work write the playbook#
Writing instructions before you've done the task is hard. You don't yet know which details will matter. Maintaining a separate document after every run is another task to remember.
cowpath starts with the work instead. A finished run holds the input, corrections and final version. The first finished run seeds a playbook. After that, every fifth run gives the agent a chance to rewrite it from what happened.
That isn't a promise that every correction becomes a permanent rule. A request for a shorter update this week might be a one-off. The agent still has to distinguish a useful pattern from a detail of one run. You can read and edit the playbook yourself.
Give each task its own path#
A sales deck and a support reply don't need the same instructions. Even a weekly customer update and a monthly board update can have different rules.
cowpath keeps a named process for each recurring task. Each process has its own playbook and history. In a team workspace, people working on the same process share that playbook, so the next person can start with the better way too.
The point isn't to save more conversations. It's to stop losing the small decisions that make a recurring task work.
Start with one task. Do it, correct it, and read what the next run starts from.