taskflow

Manage long-running multi-step tasks with persistent state and child task relationships.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zhcndoc/openclaw --skill taskflow-zhcndoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskflow
Source: https://github.com/zhcndoc/openclaw/tree/main/skills/taskflow
Command: npx skills add https://github.com/zhcndoc/openclaw --skill taskflow-zhcndoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow coordinates long-running, multi-step work so a single owner session can persist state, waits, and child tasks across restarts.

Core Features & Use Cases

  • Manages owner context, flow state, and child task linkage for durable, restartable work.
  • Supports waiting, resuming, finishing, and failure handling across detached tasks.
  • Suitable for plugin orchestration, background processing, and complex workflows that outlive a single prompt.

Quick Start

Create a new managed TaskFlow for a long-running job with a single owner session and begin tracking its progress.

Frequently Asked Questions about taskflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist state for long-running asynchronous workflows across application restarts?

To persist state for long-running asynchronous workflows across restarts, you need durable task orchestration that tracks currentStep, stateJson, and waitJson. This ensures your multi-step execution survives interruptions and resumes accurately from the last checkpoint.

What is the best way to coordinate multi-step tasks within a single owner session?

The best way to coordinate multi-step tasks within a single owner session is using a managed flow lifecycle. This approach enforces revision-checked mutations and maintains owner context, ensuring accountable and durable execution for complex background processing.

Can I manage child task relationships and wait states for background processing?

Yes, you can manage child task relationships and wait states for background processing. A durable orchestration framework links child tasks to a parent flow and persists wait conditions, allowing detached tasks to resume or finish without losing context.

When do I need durable task orchestration for complex workflows?

You need durable task orchestration for complex workflows when your processes outlive a single prompt or session. It is essential for plugin orchestration and background processing where state, waits, and child task relationships must persist across unexpected restarts.

Does task orchestration work with detached tasks that require resuming and failure handling?

Yes, task orchestration works with detached tasks by supporting waiting, resuming, finishing, and failure handling. It applies revision-checked mutations through a canonical API to ensure state integrity and accountable execution even when tasks fail or pause.

What are the limitations of relying on a single owner session for task state management?

Relying on a single owner session for task state management limits execution to that specific context's lifecycle. Without durable orchestration, complex workflows cannot persist stateJson or waitJson across restarts, causing detached child tasks to lose their progress and relationships.