execute-tasks

Drains a task tracker run by dispatching concurrent profile agents under a concurrency cap.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill execute-tasks-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-tasks
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/families/ok-planner/skills/execute-tasks
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill execute-tasks-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating many AI agents against a shared task queue is error-prone: agents can double-claim work, blow up prompt-cache efficiency with per-task messages, or overload the permission system with unbounded concurrency. This Skill runs a disciplined drain loop over the ok-planner task tracker so a filed run executes to completion without those failure modes. ## Core Features & Use Cases - Tracker drain loop: Repeatedly calls tasks next and acts on its output — starting profile agents, running exec tasks, and stopping at done or waiting. - Cache-optimized dispatch: Every agent of one profile receives the identical fixed message ("Claim your task and finish it."), so the whole first request is one cached prefix per profile per run; task ids reach agents through the atomic tasks claim protocol instead. - Concurrency cap and usage accounting: Runs at most 8 agents at once across all profiles, stamps token usage on each task as its agent returns, and handles orphaned fork tasks via tasks retry. - Use Case: After a planning ceremony files a run of implementation and review tasks into .ok-planner/bin/tasks, invoke /execute-tasks to drain the run — it starts ok-opus, ok-sonnet, and ok-haiku agents as slots free up, runs exec tasks itself, and stops when no open task remains. ## Quick Start Run the /execute-tasks slash command to drain the currently selected task tracker run until it reports done or waiting.

Frequently Asked Questions about execute-tasks

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

FAQPage Schema
How do I run multiple AI agents concurrently on a task queue?▼

Use a drain loop that calls the tracker's next command, starts as many profile agents as the printed counts allow up to a concurrency cap of 8, and repeats until next reports done or waiting. Each agent claims its own task atomically, so no two agents take the same work.

How do I preserve the prompt cache when dispatching many agents?▼

Send every agent of one profile the identical fixed message with no task id or context in it, so the whole first request is one cached prefix per profile per run. Deliver the task id through the claim command's output instead, which arrives after the cached prefix.

Can this skill decide which tasks to run or file new tasks?▼

No. It only drains what the tracker already holds: it never files tasks or items, never reads briefs or prompts, and never chooses which task an agent takes. Filing and ordering are the caller's responsibility using the tracker's own verbs.

What happens when an agent dies or a task is never claimed?▼

If an agent returns without a closed line and the next call lists an unclaimed task, the loop stops and reports it; the recovery move is tasks retry on the task left running. Orphaned fork-of tasks are retried automatically once no dispatched agent is still running.

Why is the agent concurrency capped at 8?▼

Every dispatch and every tool call an agent makes is a permission request the harness classifies one at a time, and a larger batch overloads it. The cap is 8 across all profiles unless the caller names another value when invoking the loop.