long-running-orchestrator

Coordinate long-running AI tasks with state persistence and checkpoints.

71|9|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/liangdabiao/skill-ten-prompt-generator --skill long-running-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: long-running-orchestrator
Source: https://github.com/liangdabiao/skill-ten-prompt-generator/tree/main/.claude/skills/long-running-orchestrator
Command: npx skills add https://github.com/liangdabiao/skill-ten-prompt-generator --skill long-running-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers build reliable, self-sustaining AI workflows by separating initialization from execution and by persisting task state across runs.

Core Features & Use Cases

  • Initialization-Execution separation: prepares workspace and scaffolds for long tasks.
  • State persistence & checkpoints: preserves progress to support resume after interruptions.
  • Self-correcting loops & error handling: avoids deadlocks and enables automated recovery for days-long tasks.
  • Use Case: ideal for continuous monitoring, iterative data collection, or autonomous agents that must run with minimal human supervision.

Quick Start

Tell Claude Code to set up a long-running task orchestrator for a given objective; it will generate a task workspace (todo.md, progress.log, config.json) and a worker workflow to process tasks until completion.

Frequently Asked Questions about long-running-orchestrator

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

FAQPage Schema
How do I build autonomous AI workflows that run for days without crashing?

Autonomous AI workflows require separating initialization from execution and persisting task state. This skill provides a structured prompt blueprint for deterministic task orchestration, using checkpoints and self-correcting loops to prevent deadlocks and ensure stable operation across days.

What is the best way to recover AI agent state after an interruption?

State recovery after an interruption is handled through state persistence and checkpoints. This skill preserves progress in a task workspace containing todo.md, progress.log, and config.json, enabling automated recovery and resume for multi-step workflows.

How do I set up a long-running task orchestrator for continuous monitoring?

To set up a long-running task orchestrator, tell Claude Code your objective. It generates a task workspace with todo.md, progress.log, and config.json, then scaffolds a worker workflow to process tasks until completion with minimal human supervision.

Do I need external tool dependencies for long-running agent orchestration?

No external tool dependencies are required for long-running agent orchestration. This skill operates entirely within the Claude Code Agent Skills framework, providing a structured approach to iterative data collection and multi-step workflows without external packages.

How does error handling work in days-long autonomous agent tasks?

Error handling in days-long autonomous tasks uses self-correcting loops to avoid deadlocks and enable automated recovery. The orchestrator separates initialization from execution, ensuring error states are captured and workflow execution resumes persistently.

When do I need state persistence for multi-step AI workflows?

State persistence for multi-step AI workflows is needed when tasks require continuous monitoring or autonomous operation with minimal supervision. It supports resume after interruptions by preserving progress in structured files like progress.log and todo.md.