Orchestrate long-running multi-step work with resumable state across sessions.
npx skills add https://github.com/pertain99/openclaw-better --skill taskflow-pertain99
Please help me install this Agent Skill. Skill: taskflow Source: https://github.com/pertain99/openclaw-better/tree/main/skills/taskflow Command: npx skills add https://github.com/pertain99/openclaw-better --skill taskflow-pertain99
TaskFlow lets long-running work outlive a single prompt by maintaining one owner session, one return context, and a resume point for inspection and continuation.
Create a managed flow in your tool context, spawn a child task with runTask, set waiting when awaiting input, resume when ready, and finish to close the flow.
High-intent search queries and answers about installing and using this skill.
To coordinate long-running multi-step workflows across sessions, you can use an orchestration plugin that maintains a single owner session, tracks currentStep, and provides a resume point for continued execution. It keeps business logic in caller layers.
Detached task orchestration is a technique for managing multi-step work that outlives a single prompt. You need it when jobs require persistent flow identity, state tracking, and resumable steps across different sessions or plugins.
To manage state and waiting conditions for resumable workflow steps, a flow orchestrator tracks stateJson and waitJson. You set the flow to waiting when awaiting input, then resume it when ready, ensuring revision-tracked mutations guard against conflicts.
Yes, you can link child tasks to a parent flow using runTask. This allows you to handle finish, fail, cancel, and waiting states for complex plugin workflows while maintaining one owner session and one return context.
No, this workflow orchestration approach requires no external dependencies. It operates without dependencies and delegates all business logic to caller layers like Lobster, ACPX, or plugins, keeping the orchestration logic separate.
The limitation of session-based state management is that it requires business logic to remain in caller layers. The orchestration layer only handles flow identity, state tracking, and child task linkage, meaning you must implement actual processing logic externally.
pikakitImplement multi-layer data validation across input, business logic, environment, and debugging.
enclawedManage detached task flows with persistent state and lifecycle handling.
liangdabiaoCoordinate long-running AI tasks with state persistence and checkpoints.
Agent-Pattern-LabsManage multi-step TaskFlow jobs with persistent state and owner context.
