taskflow

Coordinate long-running multi-step workflows with persistent state and child-task linkage.

121|17|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Zavianx/velaclaw --skill taskflow-zavianx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskflow
Source: https://github.com/Zavianx/velaclaw/tree/main/skills/taskflow
Command: npx skills add https://github.com/Zavianx/velaclaw --skill taskflow-zavianx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow coordinates long-running, multi-step work with a single owner context and a stable return point, enabling durable orchestration across prompts, restarts, or detached runs.

Core Features & Use Cases

  • Defines flow identity, owner session, and the source of truth for progress through currentStep, stateJson, and waitJson
  • Tracks linked child tasks, their parent flow, and overall lifecycle states (finish, fail, cancel, waiting, blocked)
  • Enforces revision-checked mutations to guard against conflicts
  • Keeps orchestration logic in the caller while hosting the flow identity and linkage
  • Use cases include plugin/tool workflows, Lobster/ACPX integrations, or any long-lived job that should persist between steps

Quick Start

Create a managed flow and then chain tasks using runTask and setWaiting as progress is made.

Frequently Asked Questions about taskflow

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

FAQPage Schema
How do I coordinate long-running tasks that need to survive restarts?

Long-running tasks survive restarts through durable orchestration with a persistent return point. TaskFlow maintains flow identity, owner context, and state across multi-step work so detached sub-tasks resume reliably without losing progress.

What is the best way to manage state for background plugin workflows?

Managing state for background plugin workflows requires tracking currentStep, stateJson, and waitJson. This skill hosts the source of truth for progress and lifecycle states, enabling background tasks to persist between steps and maintain linkage to the parent flow.

Can I link child tasks to a parent flow and track their lifecycle?

Child tasks link to a parent flow through managed-flow lifecycle tracking. The system tracks overall lifecycle states including finish, fail, cancel, waiting, and blocked, ensuring detached sub-tasks maintain their parent flow linkage throughout execution.

How does revision control prevent conflicts in task orchestration?

Revision control prevents conflicts in task orchestration through revision-checked mutations. This enforces guardrails against concurrent modifications, ensuring durable orchestration logic remains robust when multiple steps or detached runs attempt state mutations.

Does task orchestration work without external dependencies?

Task orchestration works entirely without external dependencies. The skill keeps orchestration logic in the caller while independently hosting flow identity, state persistence, and child-task linking, requiring no additional components or libraries.

When should I use detached sub-tasks instead of inline execution?

Detached sub-tasks are necessary when long-lived jobs must persist between steps or survive restarts. Any multi-step work requiring a stable return point, persistent stateJson, and durable linkage to a parent flow benefits from detached execution.