Status: Work in Progress — format stabilizing, expect changes before v1.0
Workflow definitions for multiagent teams. Each workflow defines a scheduled or manual task with agent targeting, execution mode, and markdown instructions.
spec/ # Format specification
workflow-spec.md # WORKFLOW.md format spec
workflows/ # Example workflows
kickoff/
WORKFLOW.md
pr-review/
WORKFLOW.md
...
Workflows are defined as .md files with YAML frontmatter (metadata) + markdown body (instructions).
---
id: daily-standup
name: Daily Standup
description: Async daily standup
schedule: "30 9 * * *"
executionMode: automated
targeting:
groups:
- Status
---
# Daily Standup
Each team member: post three items:
1. What you completed since last standup
2. What you plan to work on today
3. Any blockers or questionsSee spec/workflow-spec.md for the full specification.
- Schedule: cron expressions,
manual, oronce - Execution modes:
automated(no oversight) ormanaged(requires owner) - Targeting: by agents, groups, communities, or tags
- Dependencies:
dependsOnfor DAG sequencing - Secret requirements: optional
secretRequirementsmetadata for API keys, event URLs, tokens, and similar runtime inputs - Types:
once(kickoff),recurring(cron),conditional(waits for deps) - Progress: agents report 0-100% completion
Workflows can declare secretRequirements in frontmatter when they need user-provided runtime values such as API keys, slugs, URLs, or export paths.
- ClawMax can prompt for these values at run time and store them browser-local
- sensitive values do not need to be written into the markdown body
- non-sensitive values can still be echoed into the run context when appropriate
| Workflow | Schedule | Mode | Description |
|---|---|---|---|
| Team Kickoff | manual | managed | Initialize team, assign roles |
| PR Review | every 2h | automated | Review open pull requests |
| Daily Standup | 9:30am daily | automated | Async status updates |
| Pipeline Monitoring | hourly | automated | Check data pipeline health |
| Release Prep | manual | managed | Changelog, version bump, QA |
Contributions welcome. Follow the WORKFLOW.md format with YAML frontmatter.
Workflow examples must live at workflows/<id>/WORKFLOW.md, and id should be the lowercase slug of the workflow name.
ClawMax originated the WORKFLOW.md spec and the initial workflow examples in this repository.
For now:
- ClawMax-derived workflows should stay synced with the source templates in
Maximilien-ai/clawmax - Community-submitted workflows are maintained in this repository on their own terms
The intended direction is to make this repository the primary public home for the spec and workflow examples, with ClawMax eventually pulling from here instead of acting as the long-term upstream source.
Use the shared local scripts so contributor checks match CI:
./setup.sh
./format.sh
./lint.sh
./test.sh./setup.shinstalls local tooling./format.shnormalizes markdown and repo file formatting./lint.shchecks markdown and formatting without changing files./test.shruns linting plusWORKFLOW.mdvalidation
Before opening a PR, include the workflow or agent template goal, category, labels/tags, target agents, and the OpenClaw and/or ClawMax versions you tested with.
MIT