taskflow

Manage long-running multi-step tasks with persisted state and flow identity.

2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/AG064/argentum --skill taskflow-ag064
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskflow
Source: https://github.com/AG064/argentum/tree/main/skills/taskflow
Command: npx skills add https://github.com/AG064/argentum --skill taskflow-ag064

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow solves the need to run jobs that outlive a single prompt by providing a single owner context, a durable flow identity, and persisted state across restarts and detours. It ensures there is one place to inspect or resume work across prompts and sub-tasks.

Core Features & Use Cases

  • Flow identity and owner session
  • Tracks currentStep, stateJson, and waitJson
  • Links child tasks and their parent flow
  • Supports finish, fail, cancel, waiting, and blocked states
  • Revision tracking for conflict-safe mutations
  • Designed to be extended by layers like Silver, acpx, or plugins; does not own business logic

Quick Start

Create a managed flow with your tool context to begin orchestrating multi-step tasks.

Frequently Asked Questions about taskflow

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

FAQPage Schema
How do I manage long-running multi-step tasks that outlive a single prompt?

To manage long-running multi-step tasks, use a workflow orchestration approach with a single owner context and persisted state. This ensures durable flow identity across prompts, allowing you to inspect, resume, or cancel work seamlessly.

How does state persistence work for workflows that span multiple prompts?

State persistence for multi-step workflows works by tracking the currentStep, stateJson, and waitJson fields within a durable flow identity. This allows detached sub-tasks to resume safely across restarts without losing progress.

Can I track and resume detached sub-tasks linked to a parent flow?

Yes, you can track and resume detached sub-tasks by linking child tasks to their parent flow identity. The system maintains a single owner context and supports resume operations, ensuring sub-tasks reconnect properly after waiting or blocking states.

How do you handle conflict-safe mutations during task orchestration across restarts?

Conflict-safe mutations during task orchestration are handled through revision tracking. By monitoring revisions alongside the persisted stateJson, the system prevents conflicting updates when multiple operations attempt to mutate the workflow state across restarts.

Does this workflow orchestration tool support cancel and fail operations for multi-step jobs?

Yes, this workflow orchestration tool supports cancel and fail operations alongside finish, waiting, and blocked states. These operations allow you to cleanly terminate or manage multi-step jobs within the durable flow identity.

When do I need a dedicated flow identity for multi-step task orchestration?

You need a dedicated flow identity for multi-step task orchestration when jobs outlive a single prompt. It provides a single place to inspect or resume work across prompts and detached sub-tasks, ensuring consistent state management.