ClawRecipes

What is ClawRecipes?

ClawRecipes (OpenClaw Recipes) is an open-source set of “Markdown blueprints” for building OpenClaw teams and agent workflows. It focuses on file-first, versionable team context and repeatable scaffolding so teams can move from setup to shipped work in a structured, reviewable way.

The core idea is that team plans, roles, and operational workflows live as readable files. ClawRecipes also supports installing a “recipe marketplace” of team and agent templates, and defines common automation patterns such as cron-based recurring operations and an agile-like workflow lane model.

Key Features

• File-first team context in a shared workspace: keeps notes, tickets, checklists, and artifacts readable, greppable, and versioned.
• Team and agent scaffolding from known-good structures: generates lanes, roles, templates, and conventions consistently so work starts from a stable baseline.
• Role-based “Line” team composition: provides templates for Lead, Dev, DevOps, and QA roles, and lets you extend them with recipes.
• Cron automation defined as inspectable files: supports recurring operations loops that are suggested by recipes and installed via opt-in prompts.
• Workflow and execution artifacts in structured formats: includes an agile flow model (Backlog → In progress → Testing → Done) and structured “tickets/workflows” runs.
• Recipe marketplace for templates: browse marketplace entries for team recipes and agent recipes, then scaffold them into your own OpenClaw workspace.

How to Use ClawRecipes

1. Install the plugin(s) into OpenClaw using the provided commands: openclaw plugins install @jiggai/recipes.
2. Restart the OpenClaw gateway: openclaw gateway restart.
3. Scaffold a team with shared workspace context: openclaw recipes scaffold-team development-team -t my-dev-team --apply-config.
4. Alternatively scaffold a single agent (example: researcher) and apply configuration: openclaw recipes scaffold researcher --agent-id my-researcher --apply-config.
5. Browse and install additional templates from the marketplace to expand or modify your teams and recurring workflows.

Use Cases

• Create a multi-agent development team with consistent roles: use the Lead/Dev/DevOps/QA templates to structure responsibilities and generate a working shared workspace.
• Set up file-first context for ongoing execution: maintain team decisions and workflow artifacts as Markdown files so changes can be reviewed through PRs.
• Run recurring operational check-ins safely: install cron-based loops by explicit consent prompts, then reuse the same daily shape for triage, verification, and reporting.
• Standardize an agile dispatch-to-done process: scaffold workflows using the defined lane structure (Backlog, In progress, Testing, Done) with verification checklists stored as files.
• Build or extend agent toolkits for specialized tasks: scaffold a single agent role (e.g., researcher) and adjust the team structure by editing team definitions.

FAQ

• Is ClawRecipes a standalone app? No. It’s presented as an OpenClaw plugin/recipes package used with OpenClaw (including plugin install and gateway restart steps).

• How does ClawRecipes handle shared context? It uses a shared, file-based workspace where context and work artifacts are stored as Markdown notes and related items, designed to remain reviewable and versioned.

• Are cron jobs installed automatically? Cron automation is described as opt-in by default. Recipes can suggest cron jobs, but installation is prompt-gated.

• What can I scaffold with ClawRecipes? You can scaffold a team with shared workspace context or scaffold individual agents using commands shown in the Quick Start section.

• Where do templates come from? Templates are available via a “recipe marketplace,” with separate notions of team recipes and agent recipes.

Alternatives

• Other workflow automation approaches using code-defined pipelines: if you prefer defining processes directly in scripts or CI configuration rather than installing “recipes” and scaffolding files, you can implement similar loops yourself.
• General project management tooling without file-first agent workflows: tools that manage tickets and boards may not provide the same role-based multi-agent templates and git-reviewable recipe scaffolding.
• Agent orchestration frameworks that focus on runtime behavior over file-based blueprints: some solutions emphasize agent execution while offering less emphasis on keeping team context and workflows as versioned Markdown artifacts.
• Manual team scaffolding in a repository: you can recreate lanes, roles, and workflow conventions by hand, but you lose the repeatable scaffolding and marketplace-driven templates described for ClawRecipes.