taskflow

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow provides a durable flow substrate to manage long-running or detached tasks under a single owner context, ensuring continuity across prompts and restarts.

Core Features & Use Cases

  • Maintains flow identity, owner session, and requester origin.
  • Tracks currentStep, stateJson, and waitJson, and links child tasks to a parent flow.
  • Manages the lifecycle with createManaged, runTask, setWaiting, resume, finish, and cancel, with revision-safe mutations.
  • Provides clear ownership, provenance, and recovery capabilities for cross-prompt work.

Quick Start

Create a managed flow from trusted tool context and start the first task with runTask, then resume when ready and finish when complete.

Frequently Asked Questions about taskflow

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

FAQPage Schema
How do I manage state persistence for long-running background tasks?

State persistence for long-running background tasks is managed by tracking currentStep, stateJson, and waitJson under a single owner context, ensuring workflow continuity and recovery across prompts or restarts.

What is the best way to orchestrate cross-prompt workflows that outlive a single request?

Orchestrating cross-prompt workflows requires a durable flow substrate that maintains flow identity, owner session, and requester origin to ensure continuity when tasks outlive their original prompts.

How do I implement a managed flow lifecycle for detached tasks?

A managed flow lifecycle is implemented by sequentially calling createManaged, runTask, setWaiting, resume, and finish or cancel, using revision-safe mutations to link child tasks to a parent flow.

Can I link child tasks to a parent workflow and track their revisions?

You can link child tasks to a parent flow while tracking their revisions through revision-safe mutations, ensuring clear ownership, provenance, and recovery capabilities for multi-step work.

How does task recovery work for multi-step work interrupted by restarts?

Task recovery for interrupted multi-step work relies on exposed flow identity, state, and wait conditions, allowing the system to resume execution precisely where the previous session left off.

When do I need a durable flow substrate for background plugins?

A durable flow substrate is needed for background plugins when tasks outlive prompts and require state persistence, revision tracking, and explicit ownership to maintain cross-prompt workflow integrity.