workflow-orchestrator

What This Skill Does

The workflow-orchestrator is a foundational skeleton designed for developers who require structural parity with canonical queue-driven orchestration within the OpenClaw environment. It acts as a deterministic state machine for managing complex multi-stage tasks without the overhead of external plugins. The skill strictly enforces the Wave 2 execution phase ordering: detection, understanding, derivation, proposal, generation, and validation. By utilizing this orchestration engine, users ensure that their AI-driven workflows maintain a consistent, trackable, and verifiable lifecycle. The skill handles state transitions explicitly—moving from extract to create, reflect, reweave, verify, and finally done—which allows for high-fidelity resume operations in the event of an interruption.

Installation

To integrate the workflow-orchestrator, follow these steps:

1. Use the clawhub installation command: clawhub install openclaw/skills/skills/plgonzalezrx8/workflow-engine
2. Navigate to the installation directory: cd workflow-engine
3. Execute the provided setup script: ./install-hooks.sh
4. Alternatively, manually register the lifecycle routines using OpenClaw commands:
   • openclaw hooks enable session-orient
   • openclaw hooks enable write-validate
   • openclaw hooks enable session-capture

Use Cases

• Managing large-scale document processing tasks where state persistence is critical for auditability.
• Organizing complex project automation that requires multi-step derivation phases (e.g., code generation followed by security validation).
• Standardizing development workflows that rely on specific configuration files (ops/config.yaml) and task queues.
• Implementing batch processing jobs where individual file status must be tracked throughout the orchestration lifecycle.

Example Prompts

1. "workflow-orchestrator project_alpha.yaml --batch 101"
2. "orchestrate the current task queue and provide a handoff report --handoff"
3. "workflow-orchestrator target_process --type generation"

Tips & Limitations

• Tip: Always maintain your ops/derivation-manifest.md to ensure the runtime loader can restore context accurately after a restart.
• Tip: If the orchestrator fails, inspect the ops/queue/ directory to verify your YAML or JSON structure aligns with the required schema.
• Limitation: This is a skeleton implementation. It does not support external plugin hooks. Any logic requiring external API connectivity must be handled outside this orchestrator's scope.
• Limitation: The orchestrator does not execute arbitrary code; it is designed for structural coordination only, making it exceptionally safe but restricted in its direct runtime capabilities.