What is ClawRecipes?

ClawRecipes is a powerful extension for the OpenClaw framework designed to eliminate the tedious process of manually configuring AI agent teams. Instead of 'hacking agents,' users can leverage structured Markdown blueprints—called recipes—to instantly scaffold complete, cohesive, and functional agent workspaces. This system enforces a 'file-first' philosophy, ensuring that context, workflows, and team configurations are version-controlled, reviewable, and repeatable.

This solution moves team setup from fragile, hidden state management to transparent, Git-friendly infrastructure. By applying a recipe, you immediately establish shared context (like documentation and tickets), define specialized coworker-style agents (Lead, Dev, QA), lock in agile flow structures (swim lanes), and integrate recurring automation via cron jobs. The result is a deterministic, high-quality setup that goes from initial scaffold to shipped work with consistency every single time.

Key Features

• Markdown Blueprints: Define entire team structures, context repositories, and workflows using readable Markdown files, making configuration transparent and auditable.
• File-First Context (The Pantry): All critical team information—notes, tickets, checklists, and artifacts—resides in a shared, version-controlled workspace, ensuring agents never 'forget' crucial context.
• Coworker-Style Agents (The Line): Scaffold specialized roles (e.g., Lead, Dev, DevOps, QA) that operate with defined responsibilities, tools, and templates, allowing users to interact with them like dedicated team members.
• Automated Workflow Loops (The Timer): Implement recurring tasks like daily triage, board hygiene, or PR watching using cron workflows defined within recipes. These are opt-in and prompt-gated for safety.
• Agile Process Enforcement (The Pass): Automatically set up structured agile lanes (Backlog, In Progress, Testing, Done) with clean handoffs and verification checklists built directly into the workflow structure.
• Deterministic Scaffolding: Ensure every new team starts from a known-good structure, complete with pre-defined roles, templates, and conventions, guaranteeing consistency across projects.

How to Use ClawRecipes

Getting started with ClawRecipes involves integrating it into your existing OpenClaw environment and then applying the desired recipe to build your team structure.

1. Installation: First, install the plugin into your OpenClaw setup via the terminal:

$openclaw plugins install @jiggai/recipes

After installation, you must restart the OpenClaw gateway to activate the new functionality:

$openclaw gateway restart

2. Scaffolding a Team or Agent: Once installed, you can use the scaffold-team command to deploy a full, pre-configured environment based on a recipe. For example, to set up a standard development team:

$openclaw recipes scaffold-team development-team -t my-dev-team --apply-config

Alternatively, if you only need a single specialized agent, you can scaffold it directly:

$openclaw recipes scaffold researcher --agent-id my-researcher --apply-config

3. Review and Iteration: Because all configurations are file-based, you can immediately review the generated workspace structure, inspect the agent roles, and modify the agile lanes or cron jobs in your version control system before fully deploying or running the agents.

Use Cases

1. Rapid Project Kickoffs: Instantly launch standardized development environments for new projects. A recipe can enforce company-wide standards for code review checklists, deployment procedures (DevOps role), and initial documentation structure, ensuring no critical setup step is missed.
2. Automated Research & Reporting: Deploy a team centered around a Researcher agent supported by a QA agent. Use the cron feature to schedule daily data aggregation or market monitoring tasks, delivering consistent, repeatable reports without manual intervention.
3. Enforcing Agile Discipline: For teams struggling with process adherence, a ClawRecipe can lock in a strict agile flow (Dispatch -> Backlog -> In Progress -> Testing -> Done). The structure itself guides the agents and human contributors toward proper handoffs and verification steps.
4. Onboarding New Developers: New team members can clone a repository containing the project's ClawRecipe configuration. This immediately sets up their local OpenClaw environment with the exact same agent roles, context files, and workflow expectations as the rest of the team.
5. Maintaining Infrastructure as Code (IaC) Workflows: Use recipes to define agents responsible for infrastructure management (DevOps). Their context can include IaC templates, and their workflows can be set to run automated safety checks or deployment verification loops on a schedule.

FAQ

Q: Is ClawRecipes free to use with OpenClaw? A: ClawRecipes is presented as an open plugin (@jiggai/recipes) for OpenClaw. While the plugin itself is generally open-source and free to install, usage costs are dependent on the underlying OpenClaw gateway infrastructure and the LLM providers you utilize.

Q: How do I customize the roles defined in a recipe (e.g., change the Dev agent's tools)? A: Since recipes use file-based blueprints, you can inspect the scaffolded files after deployment. You can modify the agent definitions (tools, templates, responsibilities) directly in the generated configuration files within your workspace and commit those changes to version control.

Q: What happens if a cron job defined in a recipe runs unexpectedly? A: ClawRecipes prioritizes safety. Cron jobs suggested by a recipe are installed only after explicit user consent via a prompt. They are not automatically activated upon scaffolding, preventing unwanted background operations.

Q: Can I share my custom team setups with others? A: Absolutely. The core benefit of the file-first approach is shareability. You can commit your modified recipe files or the resulting scaffolded workspace structure to Git and share it with any other OpenClaw user who has the ClawRecipes plugin installed.

Q: What if I need a role not included in the standard recipes (e.g., a dedicated Marketing agent)? A: You can extend existing recipes or create new ones. The system allows you to define custom roles, assign them specific tools and templates, and integrate them into the existing agile lanes, ensuring your specialized needs are met within the structured framework.