Guides/Workflows
Reusable AI Agent Workflows: Capture a Procedure Once, Run It Every Month
Turn a procedure your agent worked out into a workflow in the knowledge base: flows and steps any agent can find by phrase, follow exactly, and adapt to a new client or entity.
Jose R. Gonzalez, CPA · Founder of ContxOS
Updated · 2 min read
In short
A ContxOS workflow is a procedure stored in the knowledge base as a tree: the workflow, its flows (stages) and its workers (individual steps), with variants for entity-specific details. Agents find workflows by search or phrase and read each step just before executing it. One workflow can serve many clients: the generic procedure stays shared, and each client’s specifics live in its own variants.
Why prompts are not procedures
An agent can work out a complex procedure once, such as a month-end reconciliation, a release checklist or a data migration. Next month it has to work it out again, and it will do it slightly differently. Saved prompts help a little, but they cannot hold a twenty-step process with branches, exceptions and hard-won lessons.
How a workflow is organized
- Workflow: the whole procedure, its purpose and its rules.
- Flows: the stages, in order.
- Workers: the individual steps, each with exact instructions.
- Variants: the parts that differ per client, entity or environment, kept separate from the shared procedure.
Lessons learned during a run are folded back into the step they belong to, so the next run starts from the improved version.
Building and editing
Tell your agent "new workflow" and describe the procedure, or have it capture a procedure it just performed. "edit workflow" changes an existing one. Edits are applied as one batch, with a dry run first, so a workflow is never left half-changed. You can also edit workflows directly in the ContxOS dashboard.
Proof: the port gets cheaper every time
In one accounting practice running on ContxOS, a bank-feed clearing workflow took about two weeks to invent and harden for the first company. It was ported to a second company 13 days later. It was ported to a third company, which had a completely different entity structure, in a single day, and it ran live that evening.
The generic procedure carried over. Only the company-specific variants were new.
What to ask your agent
With ContxOS connected to Claude or another MCP client, requests like these work as written:
new workflow: the monthly close checklist we just ran
Find the workflow for onboarding a new client and walk me through its flows.
edit workflow: add a step before posting that checks control totals
Adapt the bank-feed workflow for the new entity. Keep the shared steps and add its variants.
Limits and requirements
- Workflows are followed by your agent. Their quality depends on the model you use and on how precisely each step is written.
- Agents read a step immediately before executing it, not the whole tree up front. This keeps context lean, but a very large workflow takes several reads.
Frequently asked questions
How is this different from Claude Skills?
Skills package instructions for a model to load. ContxOS workflows are records in a shared knowledge base: searchable, linked to the decisions behind them, edited as a batch, and tracked across runs. The two work together. ContxOS installs its own commands as skills.
Can I see a workflow without running it?
Yes. Ask for a compact map of any workflow, or open it in the dashboard’s workflow editor.
Give your agent a memory that lasts
Connect ContxOS to Claude in about a minute. The free plan includes one project.