workflow-orchestration
Chains multiple skills into a named multi-step workflow with conditions and state tracking. Use when a recurring task requires the same sequence of skills every time.
git clone --depth 1 https://github.com/ArchieIndian/openclaw-superpowers /tmp/workflow-orchestration && cp -r /tmp/workflow-orchestration/skills/openclaw-native/workflow-orchestration ~/.claude/skills/workflow-orchestrationSKILL.md
# 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> 2. <skill-name>: <brief instruction> [on_failure: <skill-name>] 3. <skill-name>: <brief instruction> ``` ## Running a Workflow ### Step 1: Load or Create - If a workflow named `<name>` exists in state, load it and check `current_step` - If new, write workflow definition to state with `status: in_progress`, `current_step: 1` ### Step 2: Execute Current Step - Announce: "Workflow `<name>` — step [N]: invoking `<skill-name>`" - Invoke the skill with its instruction - If step succeeds: advance `current_step`, update `last_updated` - If step fails and `on_failure` is set: invoke the fallback skill, then continue - If step fails with no fallback: set `status: blocked`, write `blocked_reason`, stop and notify user ### Step 3: Repeat Until Done Continue until all steps complete. Set `status: complete`. ## Key Principles - One active workflow at a time per state file - Always announce which step you're on so the user can follow along - Never silently skip a step — blocked is better than wrong
Syncs agent daily memory and MEMORY.md to an Obsidian vault so notes are human-browsable. Use nightly or on demand.
Structured ideation before any implementation. Use when starting any non-trivial task.
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.
Executes plans task-by-task with verification. Use when implementing a plan.
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
Crawls a new codebase to infer stack, conventions, and key invariants, then generates a PROJECT.md context file for the agent
Handles PR review feedback by fetching comments, grouping issues, fixing one group at a time, and verifying before replies.
Detects skill name shadowing and description-overlap conflicts that cause OpenClaw to trigger the wrong skill or silently ignore one when two skills compete for the same intent.