taskflow

Coordinate long-running multi-step tasks with persistent state across restarts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow provides a durable flow substrate to coordinate jobs that outlive a single prompt, maintaining one owner session, one return context, and one place to inspect or resume work.

Core Features & Use Cases

  • Managed-flow lifecycle: createManaged, runTask, setWaiting, resume, finish, and cancel with revision tracking.
  • Persistence and cross-session continuity: stateJson and waitJson enable resilience across restarts and external waits.
  • Parent-child task linkage: links child tasks to the parent flow for coherent end-to-end monitoring.
  • Durable ownership and identity: flows carry owner session and requester origin for traceability.
  • Use cases include plugin or tool orchestration, cross-service workflows, and long-running background tasks.

Quick Start

Create a managed flow for a multi-step job and resume it after waiting states.

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 multi-step tasks across restarts?

Coordinate long-running multi-step tasks across restarts by using a durable flow substrate that maintains persistent state, owner sessions, and linked child tasks. This ensures cross-session continuity and reliable workflow orchestration upon resumption.

What is the best way to manage workflow state and external waits for background jobs?

Manage workflow state and external waits by applying managed-flow lifecycle methods like setWaiting and resume. Persistent stateJson and waitJson variables enable resilience across restarts and external waits for background jobs.

How do I link child tasks to a parent workflow for end-to-end monitoring?

Link child tasks to a parent workflow by using durable ownership and identity features. Flows carry owner session and requester origin data, linking child tasks to the parent flow for coherent end-to-end monitoring across services.

Can I use a single owner session to orchestrate plugin and tool workflows?

Yes, you can orchestrate plugin and tool workflows using a single owner session. The durable flow substrate maintains one return context and provides managed-flow lifecycle methods for coherent plugin runtime execution.

Does this managed-flow lifecycle support cross-service workflows and detached tasks?

The managed-flow lifecycle supports cross-service workflows and detached tasks by tracking state revisions across methods like createManaged, runTask, resume, and cancel. This ensures durable task persistence across external waits.

Why do I need persistent state and revision tracking for background task orchestration?

Persistent state and revision tracking are needed for background task orchestration to prevent data loss during restarts. Tracking revisions across lifecycle methods guarantees that external waits and parent-child task linkages remain coherent.