Workflow Engine

Verified

Structural parity skeleton for queue-driven orchestration in a workflow context.

352 downloads

$ Add to .claude/skills/

$ openclaw install

About This Skill

Contract

This skill is intentionally skeleton-only. It provides structure parity with canonical queue orchestration without plugin hooks.

Wave 2 execution parity includes:
Setup derivation phase ordering: `detection -> understanding -> derivation -> proposal -> generation -> validation`
Required persisted setup artifacts: `ops/derivation.md`, `ops/derivation-manifest.md`, `ops/config.yaml`
In-skill lifecycle emulation routines (not real hook execution):
- session orient
- write-time validation checklist
- stop/session capture persistence

Argument Parsing

Parse arguments in this order:
positional `target` (optional)
`--handoff` (boolean)
`--batch <id>` (optional)
`--type <phase>` (optional)
unknown flags are non-fatal; report and ignore

If no `target` is supplied, list candidate inbox files and request explicit selection.

Runtime Loader Requirements

Before doing queue work, load runtime context from:
`ops/derivation-manifest.md` (if present)
`ops/config.yaml` (if present)
queue file with fallback precedence:
1. `ops/queue/queue.yaml`
2. `ops/queue/queue.yml`
3. `ops/queue/queue.json`

If no queue file exists, fail safely with actionable remediation.

Safety Constraints

Never:
execute arbitrary shell from user-provided strings
continue processing after parse/load failures
mutate tasks outside declared queue schema fields
call external plugins/hooks (explicitly out of scope)

Always:
validate queue structure before state transitions
make state transitions explicit (`extract -> create -> reflect -> reweave -> verify -> done`)
produce deterministic handoff text when `--handoff` is set
preserve resumability by reading persisted queue state first

Scope Boundary

No plugin hooks are implemented in this skeleton. Lifecycle behavior is emulated in-skill to preserve deterministic execution semantics only.

Installation

To install the workflow-engine and enable its hooks:

```bash # Clone or navigate to the workflow-engine directory cd workflow-engine

# Run the install script to set up hooks ./install-hooks.sh

# Or manually enable hooks via openclaw openclaw hooks enable session-orient openclaw hooks enable write-validate openclaw hooks enable session-capture ```

Use Cases

Build queue-driven orchestration systems for multi-step workflows
Implement task queuing and execution patterns for background processing
Design workflow architectures with proper state management and error handling
Create skeleton implementations for workflow orchestration services
Coordinate multi-service workflows with reliable message passing

Pros & Cons

Pros

+Queue-driven architecture ensures reliable task execution and retry
+Structural skeleton approach provides a starting point for custom implementations
+Addresses the fundamental need for workflow orchestration in backend systems

Cons

-Skeleton only — requires significant implementation to become production-ready
-No specific queue technology recommendation or integration

FAQ

What does Workflow Engine do?

Structural parity skeleton for queue-driven orchestration in a workflow context.

What platforms support Workflow Engine?

Workflow Engine is available on Claude Code, OpenClaw.

What are the use cases for Workflow Engine?

Build queue-driven orchestration systems for multi-step workflows. Implement task queuing and execution patterns for background processing. Design workflow architectures with proper state management and error handling.

100+ free AI tools

Writing, PDF, image, and developer tools — all in your browser.

AI Humanizer

Make AI text undetectable

AI Detector

Free, unlimited

PDF Tools

Merge, split, compress

Next Step

Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.

Open Free Tools Try AI Detector