taskflow

Orchestrate multi-step background tasks with a resumable managed flow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow eliminates the fragility of coordinating multi-step or long-running work across detached runs by giving all steps a single durable flow identity that can be resumed safely.

Core Features & Use Cases

  • Durable managed flows: Create a managed flow that persists owner context and linkage across createManaged, runTask, setWaiting, resume, and finish/fail/cancel.
  • Revision-checked state mutations: Safely evolve stateJson, currentStep, and wait metadata with conflict-aware expected revisions.
  • Child-task orchestration: Run linked child tasks under the same flow so orchestration, waiting, and inspection remain coherent.
  • Use case: When your agent triages an inbox over multiple asynchronous steps (classify, wait for replies, then finalize), TaskFlow keeps one owner session and a resumable state bag instead of scattering progress across unrelated jobs.

Quick Start

Use the taskflow skill to create a managed flow for your plugin’s long-running job, then drive it through run, waiting, resuming, and completion steps.

Frequently Asked Questions about taskflow

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

FAQPage Schema
How do I manage state for asynchronous multi-step jobs across detached runs?

To manage state for asynchronous multi-step jobs, use a durable managed flow that persists owner context and linkage across detached runs. This provides a single resumable flow identity, ensuring background execution returns one coherent outcome per owner session.

What is the best way to resume a background workflow after waiting for external events?

The best way to resume a background workflow after external events is to drive the task lifecycle through createManaged, runTask, setWaiting, resume, and finish APIs. This allows the job to pause and resume safely without losing state linkage.

How does revision control work for workflow orchestration state mutations?

Revision control for workflow orchestration applies conflict-aware expected revisions to safely evolve stateJson, currentStep, and waitJson. This prevents concurrent detached steps from overwriting each other's state changes during multi-step execution.

Can I run linked child tasks under the same owner context for background execution?

Yes, you can run linked child tasks under the same managed flow owner context. This ensures child-task orchestration, waiting, and inspection remain coherent within one resumable flow identity instead of scattering progress across unrelated jobs.

Why does my async task lose linkage when triaging an inbox over multiple classification steps?

Async tasks lose linkage during multi-step inbox triage because detached runs scatter progress across unrelated jobs. Using a managed flow with a durable owner session and a resumable state bag keeps all steps linked to one coherent outcome.