taskflow

Coordinate and persist multi-step tasks with durable state and owner context.

Updated Dec 6, 2016
One-click install
npx skills add https://github.com/majunbao/learn --skill taskflow-majunbao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taskflow
Source: https://github.com/majunbao/learn/tree/main/openclaw_tags/openclaw-2026.4.24/skills/taskflow
Command: npx skills add https://github.com/majunbao/learn --skill taskflow-majunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and preserves long-running, multi-step tasks as a single durable TaskFlow with an owner context, persistent state, waits, and child tasks.

Core Features & Use Cases

  • Durable flow identity and owner session tracking for introspection and resumption
  • Managed lifecycle: createManaged, runTask, setWaiting, resume, finish or fail
  • Linkage between parent flows and child tasks, with revision-safe mutations
  • Works across restarts and tool contexts for plugin-style orchestration

Quick Start

Create a managed TaskFlow, run a task, wait for completion or external input, and resume to finish

Frequently Asked Questions about taskflow

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

FAQPage Schema
How do I coordinate multi-step tasks that wait for external inputs across sessions?▼

Long-running multi-step tasks are coordinated by persisting a single durable flow with owner context, wait states, and revision tracking across sessions. It uses a managed lifecycle to create, run, wait, resume, and finish tasks requiring external inputs.

What is the best way to preserve workflow state and ownership across application restarts?▼

Workflow state and ownership are preserved across restarts using durable flow identity and owner session tracking. The flow persists state and wait configurations, enabling introspection and resumption of long-running workflows after tool or context restarts.

How do I manage parent and child tasks in a long-running workflow?▼

Parent and child tasks are managed through built-in linkage that connects parent flows with child tasks using revision-safe mutations. This ensures traceability and durable state ownership while coordinating sub-tasks within the same long-running workflow.

Can I use durable state management for plugin-style task orchestration?▼

Durable state management works across restarts and tool contexts for plugin-style orchestration. It applies a canonical runtime API to manage the flow lifecycle, ensuring multi-step tasks maintain flow identity and wait state persistence.

When do I need durable flow identity for task orchestration?▼

Durable flow identity is needed for long-running workflows that wait on external inputs or sub-tasks and require persistent state. It provides owner session tracking, introspection, and resumption capabilities for multi-step tasks across sessions.