task-system

Execute long-running build, test, deploy, and data-analysis tasks in the background.

5|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/TechyMT/claude-code-superpowers --skill task-system-techymt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-system
Source: https://github.com/TechyMT/claude-code-superpowers/tree/main/skills/task-system
Command: npx skills add https://github.com/TechyMT/claude-code-superpowers --skill task-system-techymt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running operations often block the main conversation loop, making the UX sluggish. The Task System decouples background work from the chat, writing outputs to a disk-backed file and exposing a clear lifecycle.

Core Features & Use Cases

  • Spawns background tasks from tools or commands and tracks status in AppState.tasks.
  • Streams output to a disk file (with outputOffset) so results persist across restarts and can be tailed.
  • Supports multiple task types (local_bash, local_agent, remote_agent, in_process_teammate, local_workflow, monitor_mcp, dream) and lifecycle states (pending, running, completed, failed, killed).
  • Enables users to monitor progress with /tasks, cancel tasks with /tasks kill, and observe results asynchronously in the conversation.

Quick Start

Start a background task by registering a new task in AppState with a unique ID and let it run without blocking the conversation.

Frequently Asked Questions about task-system

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

FAQPage Schema
How do I run long-running tasks in the background without blocking the chat loop?

You can run long tasks in the background without blocking by spawning them as background tasks that execute asynchronously, tracking their status in a task registry within AppState while continuing your conversation.

How does disk-backed output streaming work for background tasks?

Disk-backed output streaming writes task results to a file on disk using an output offset, allowing outputs to persist across restarts and be tailed asynchronously without losing progress data.

What task lifecycle states are supported for asynchronous background operations?

Asynchronous background operations support a defined task lifecycle with five states: pending, running, completed, failed, and killed, allowing precise tracking of long-running work from start to finish.

Can I use background tasks for local bash commands and remote agent workflows?

Yes, background tasks support multiple task types including local_bash, local_agent, remote_agent, local_workflow, and monitor_mcp, enabling asynchronous execution across local or remote contexts.

How do I monitor progress and cancel running background tasks?

You can monitor progress with the /tasks command and cancel running tasks using /tasks kill, observing results asynchronously in the conversation as they stream to disk.

What is the best way to decouple build and deploy operations from the main conversation?

The best way to decouple build and deploy operations is to register them as background tasks in AppState with a unique ID, letting them run without blocking the conversation while streaming output to disk.