workflow-orchestration
Workflow Orchestration
State file: ~/.openclaw/skill-state/workflow-orchestration/state.yaml
A workflow is a named sequence of skill invocations with optional conditions. Define it once, run it reliably every time.
When to Use
- A recurring task always follows the same skill sequence (e.g. review → plan → execute → verify)
- A multi-step process needs to resume if interrupted
- You want conditional branching: "if step 2 fails, run skill X instead"
Defining a Workflow
A workflow is defined inline as:
workflow: <name>
steps:
1. <skill-name>: <brief instruction>
More from archieindian/openclaw-superpowers
context-window-management
Prevents context overflow on long-running OpenClaw sessions. Use when approaching context limits.
28heartbeat-governor
Enforces per-skill execution budgets for scheduled cron skills — pauses runaway skills that exceed their token or wall-clock budget before they drain your monthly API allowance.
27using-superpowers
Bootstrap skill — teaches the agent how to find and invoke skills. Use when starting any new task or session.
23long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
22fact-check-before-trust
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
21persistent-memory-hygiene
Keeps OpenClaw's memory store clean, structured, and useful. Use at session end and during periodic maintenance.
20