taskflow

Manage detached task flows with persistent state and lifecycle handling.

2|Updated May 23, 2026

Search Tags:#subagents #orchestration #state-management #background-jobs #taskflow #revision-control

Ready to run

npx skills add https://github.com/enclawed/enclawed-oss --skill taskflow-enclawed

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: taskflow
Source: https://github.com/enclawed/enclawed-oss/tree/main/skills/taskflow
Command: npx skills add https://github.com/enclawed/enclawed-oss --skill taskflow-enclawed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow keeps multi-step work that outlives one prompt organized under one owner context, so detached tasks can pause, resume, and finish without losing state.

Core Features & Use Cases

Manages flow identity, owner session, requester origin, and child-task links.
Tracks currentStep, stateJson, waitJson, revisions, and lifecycle states like waiting, blocked, finished, failed, and canceled.
Fits managed orchestration for inbox triage, approvals, subagent work, and other jobs that need durable progress across restarts.

Quick Start

Use TaskFlow to create a managed flow, run a child task, record waiting state, and resume or finish it with revision-safe updates.

Frequently Asked Questions about taskflow

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

FAQPage Schema

How do I manage background tasks that need to pause and resume across multiple prompts?▼

Detached task orchestration manages long-running work across prompts by preserving flow identity, owner session, and requester origin so background tasks can pause, resume, and finish without losing state. It tracks currentStep, stateJson, and waitJson for durable progress.

What is the best way to preserve state for subagent workflows during a system restart?▼

Subagent state preservation during restarts relies on persistent stateJson and waitJson records with revision-checked mutations. This ensures managed orchestration flows maintain their waiting, blocked, or running lifecycle states and can safely resume after a restart.

How do I handle lifecycle events like cancel or fail for orchestrated child tasks?▼

Orchestrated child-task lifecycle handling uses safe cancel, fail, finish, and runTask operations to manage detached flows. These operations preserve revision-checked mutations and update lifecycle states, ensuring parent and child task links remain intact across waiting or blocked conditions.

Can I use taskflow for inbox triage and approval workflows that need durable progress?▼

Yes, managed orchestration fits inbox triage, approvals, and subagent work that require durable progress across restarts. The system tracks waiting states and child-task links, allowing approval workflows to pause for input and resume with revision-safe updates.

Does taskflow work without external dependencies for state management?▼

Yes, taskflow operates with no external dependencies and manages state internally through persistent stateJson and waitJson. It applies revision control to mutations and handles the full runTask lifecycle without requiring additional plugins or libraries.