executing-tasks

Orchestrate ready task execution across sessions, tmux, or scheduled tasks.

3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kazukinagata/waggle --skill executing-tasks-kazukinagata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-tasks
Source: https://github.com/kazukinagata/waggle/tree/main/skills/executing-tasks
Command: npx skills add https://github.com/kazukinagata/waggle --skill executing-tasks-kazukinagata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, claude, and includes scripts (resource) components.

What problem does it solve?

Orchestrates the end-to-end execution of ready tasks across single or multiple execution modes.

Core Features & Use Cases

  • Automated selection of Ready tasks with concurrency control and dynamic mode selection (current session, tmux parallel, or Claude Desktop scheduled tasks)
  • Provider detection and identity resolution to ensure proper context before dispatch
  • Working directory validation and readiness checks to guarantee task execution safety
  • Flexible dispatch orchestration including in-session execution, parallel tmux, or scheduled task creation for scalable workflows

Quick Start

Issue the command to start the next ready task in your current session.

Frequently Asked Questions about executing-tasks

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

FAQPage Schema
How do I orchestrate autonomous tasks across multiple execution modes?

Task orchestration across execution modes is handled by selecting ready tasks and dispatching them via current sessions, tmux parallel runs, or Claude Desktop scheduled tasks. The system validates provider identity, checks working directories, and enforces readiness before dispatching.

Can I use tmux for parallel task execution with Claude?

Yes, tmux-based parallel runs are supported as a dispatch mode. The orchestrator selects ready tasks and executes them concurrently across tmux sessions, ensuring workspace validation and provider identity resolution occur before dispatch.

What readiness checks are required before dispatching task workflows?

Readiness checks ensure core fields exist, working directories are validated, and provider identity is resolved before dispatch. This guarantees task execution safety and proper context setup for the selected execution mode.

Does this task orchestration approach work with Claude Desktop scheduled tasks?

Yes, Claude Desktop scheduled tasks are one of the supported execution modes. The orchestrator can create scheduled task entries for scalable workflows, applying provider detection and workspace validation before dispatch.

What's the best way to manage concurrency when executing ready tasks?

Concurrency control is managed automatically during task selection. The orchestrator identifies ready tasks and applies dynamic mode selection—current session, tmux parallel, or scheduled—while enforcing readiness checks to ensure safe parallel execution.

Why does task dispatch fail when the working directory is invalid?

Task dispatch fails because working directory validation is a mandatory readiness check. The orchestrator enforces this to guarantee execution safety, ensuring the workspace context is correct before any task is dispatched across execution modes.