Stop hacking agents. Start cooking with recipes.
ClawRecipes builds multi-agent teams out of markdown. Shared context as files, specialist roles on the line, scheduled workflows, and a process that verifies its own work.
openclaw plugins install @jiggai/recipesPlugin installs
30,292 to date, per npm
Monthly installs
1,275 in August 2026, per npm
In production
Running, not a preview
What it looks like without this.
Every one of these is a process problem wearing a tooling costume. They are the reason the plugin exists.
The prompts that actually work live in one person’s head.
Roles and context as markdown files on disk — readable, diffable, and reviewable like anything else you version.
Every agent has to be re-told what the project is before it can help.
A shared pantry of context that every agent on the team reads from the same source.
An agent said it was done. It was not done.
Verification checklists per step. Work reaches Done when the checks pass, not when an agent claims it.
Something ran overnight that nobody agreed to.
Automation is opt-in by default, and every scheduled run leaves a record of what it did.
Changing how the team works means rewriting the whole setup.
Swap a role’s model, tools or responsibilities without touching the workflow around it.
Agents do not need better prompts. They need a process that can tell whether the work is finished.
Which is why a recipe is a markdown file on disk rather than a setting in a dashboard: the process has to be reviewable by the same people who review the code.
Four stations, one workflow.
A recipe is a markdown file. Everything else — who works on it, when it runs, how it gets checked — is defined in the same place.
The Pantry
Everything the team needs lives as files in a workspace directory — markdown briefs, tickets, checklists. Agents read the same source of truth your people do, and because it is all plain text, every change shows up in a diff.
- File-first, and yours to version
- Readable without the tool that wrote it
- Deterministic scaffolding
The Line
Prebuilt specialist roles — Lead, Dev, DevOps, QA — that you assign like staff. Swap models, tools, or responsibilities per role without rewriting your workflow.
- Prebuilt specialist roles
- Per-role model + tool config
- Custom roles when you need them
The Timer
Recurring work runs on a schedule: nightly triage, weekly reports, hourly monitors. Automation is opt-in by default, so nothing runs that you did not agree to.
- Cron-scheduled runs
- Opt-in consent model
- Per-run history and output
The Pass
Work moves through swim lanes with verification checklists at each step. Nothing reaches Done because an agent claimed it did — it reaches Done when the checks pass.
- Backlog → In Progress → Testing → Done
- File-based verification checklists
- Evidence attached to each step
What lands on disk.
Files, not configuration. Which means the whole setup is readable, diffable and revertible.
A pantry of shared context
Briefs, standards and checklists as markdown, read by every agent on the team and edited by the people who know the answers.
Roles you can staff
Lead, Dev, DevOps, QA and a workflow runner out of the box, each with its own model and tool budget, swappable without rewriting the workflow.
Schedules that ask first
Cron-driven recipes that stay opt-in, so nothing starts running against your work because a default said it could.
A definition of done
Verification checklists attached to each step, with the evidence kept alongside the work rather than asserted in a summary.
Three commands, then it is running.
It is an OpenClaw plugin, so there is no separate service to stand up and nothing to host.
openclaw plugins install @jiggai/recipes01✓ installed @jiggai/recipes
The plugin, registered with your existing OpenClaw install.
openclaw recipes scaffold-team development-team -t devteam --apply-config02✓ ok · 5 agents · workspace-devteam
A team workspace on disk — role folders, ticket lanes and shared context — as plain markdown you can read and edit.
openclaw recipes dispatch --team-id devteam --request "Add SSO to admin"03✓ ticket 0007 · backlog · owner dev
A request turned into a numbered ticket the team works through lane by lane, rather than a prompt somebody has to babysit.
Who this is for — and who it isn't.
It is a real tool with real edges. Better you find out here than three days in.
- Work that more than one agent touches, on a team more than one person answers for
- You want the process written down in files you can put under version control
- You need to be able to say why an agent did something, weeks later
- One-off prompting. A recipe is overhead you would not get back
- You want a hosted, no-code builder. This is markdown on your own machine
- Nobody on your side is willing to open a text file
ClawKitchen
ClawRecipes defines the teams and workflows. ClawKitchen puts them on a board you can watch while they run. Most people end up with both.
The questions we get asked.
Why markdown rather than a UI?
Because the process has to survive review. A file changes with an author and a reason, and you can put the workspace under version control and see it in a diff. A setting in a dashboard changes silently and nobody finds out until a run behaves differently.
Does this lock me into your tooling?
The recipes are markdown in a directory you own. If you stop using the plugin, the files stay where they are and you keep readable documentation of how your team worked — which is more than most workflow tools leave behind.
What stops a scheduled recipe running something destructive?
Automation is opt-in per recipe rather than on by default, runs are recorded, and the verification step has to pass before work moves forward. It is not a substitute for review, and it does not pretend to be.
Do I need ClawKitchen too?
No. ClawRecipes runs from the CLI on its own. ClawKitchen adds the board and the run history if you would rather watch it than tail it.
What does it cost?
Nothing. The plugin is free and public. We make money consulting, and the plugins are the proof that we run this stuff ourselves.
Install it in one command.
ClawRecipes is an OpenClaw plugin. If you already run OpenClaw, you are one install away. ClawKitchen pairs with it.
openclaw plugins install @jiggai/recipesWant this running on your own work?
The plugin is free and public. If you would rather someone set it up around your operation, that is what the consulting side does.