Long Task Coordinator

If your work spans multiple sessions, gets handed off to other agents, or needs to survive interruptions, this keeps a single durable state file as the source of truth instead of relying on chat history. It enforces a clear cycle: read state, recover if needed, decide next action, persist changes, then report. The key insight is treating "awaiting result" as a legitimate status rather than a failure, and separating recovery logic from actual domain work. Skip it for quick single-turn tasks, but reach for it when losing context mid-stream would actually hurt. Works with Read, Write, Edit, Bash, and the usual file tools.

skills.sh installs: 599
GitHub stars: 66
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add charon-fan/agent-playbook --skill long-task-coordinator --agent claude-code

Installs into .claude/skills of the current project.

Files

Long Task Coordinator

Keep long-running work recoverable, stateful, and honest.

When to Use This Skill

Use this skill when the work:

Spans multiple turns or multiple sessions
Involves handoffs to workers, subagents, or background jobs
Needs explicit waiting states instead of "still looking" updates
Must survive interruption and resume from a durable state file

Skip this skill for small, single-turn tasks. Use planning-with-files when simple planning is enough and recovery logic is not the main concern.

Related Skills

planning-with-files keeps multi-step work organized in files.
workflow-orchestrator chains follow-up skills after milestones.
long-task-coordinator makes long-running work resumable, auditable, and safe to hand off.