taskflow

Orchestrate long-running multi-step tasks with state persistence and lifecycle events.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/191854169/openclawFork --skill taskflow-191854169
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskflow
Source: https://github.com/191854169/openclawFork/tree/main/skills/taskflow
Command: npx skills add https://github.com/191854169/openclawFork --skill taskflow-191854169

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow enables long-running work that spans multiple prompts or detached tasks while preserving a single owner context, a consistent return value, and a centralized resume point.

Core Features & Use Cases

  • flow identity, owner session and requester origin
  • currentStep, stateJson, and waitJson
  • linked child tasks and their parent flow id
  • finish, fail, cancel, waiting, and blocked state
  • revision tracking for conflict-safe mutations It does not own branching or business logic; keep domain logic in the caller or agents.

Quick Start

Create a managed TaskFlow, then sequence createManaged, runTask, setWaiting, resume, and finish to run a multi-step workflow.

Frequently Asked Questions about taskflow

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

FAQPage Schema
How do I manage workflow state for long-running multi-step tasks across detached prompts?

Task orchestration for detached tasks uses a single owner session to persist workflow state, tracking currentStep, stateJson, and waitJson to preserve context and provide a centralized resume point across interruptions.

What is the best way to resume a long-running workflow after an interruption?

Workflow resumption relies on centralized state persistence and lifecycle events like waiting and blocked. By linking child tasks to a parent flow identity, the owner session can safely resume orchestration from the last recorded step.

How do I coordinate detached sub-tasks without losing the parent flow identity?

Detached sub-tasks are coordinated by linking them to a parent flow identity managed by a single owner session, ensuring consistent return values and centralized revision tracking for conflict-safe mutations.

Does this workflow orchestration approach handle branching and business logic?

Workflow orchestration here does not own branching or business logic. It strictly manages flow identity, state persistence, child task linking, and lifecycle events, leaving domain logic to the caller or agents.

How do I sequence a multi-step workflow with lifecycle events like finish, fail, and cancel?

Multi-step workflow sequencing follows a createManaged, runTask, setWaiting, resume, and finish pattern. This applies lifecycle events such as finish, fail, cancel, waiting, and blocked to manage task transitions safely.

When do I need revision tracking for conflict-safe mutations in task orchestration?

Revision tracking is needed for conflict-safe mutations when long-running workflows span multiple prompts and detached tasks, ensuring that concurrent state updates to flow identity and stateJson do not overwrite each other.