sum-dispatch

Delegates approved work to isolated Herdr worker agents with durable task briefs.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/douglasjarquin/sum --skill sum-dispatch-douglasjarquin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sum-dispatch
Source: https://github.com/douglasjarquin/sum/tree/main/skills/sum-dispatch
Command: npx skills add https://github.com/douglasjarquin/sum --skill sum-dispatch-douglasjarquin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-agent coding work manually means losing track of which agent runs which task, on which model, and in which checkout. This Skill turns an explicitly approved user request into a durable worker brief, an isolated Herdr worktree, and a registered worker agent, while the coordinator stays free for inbox notices. ## Core Features & Use Cases - Controlled dispatch: Creates a task brief from the user's words, prepares a separate Herdr worktree, launches the selected worker harness, and registers the pane as that task's worker. - Capacity and execution management: Enforces configured worker limits, supports parking and resuming stopped attempts, and bounds repair iterations with explicit human grants. - Launch specification resolution: Translates natural-language harness/model choices into explicit flags, saved defaults, or presets, with fixed precedence and refusal of unverified flags. - Use Case: A user says "Use Codex to fix the failing login test in my repo, run the checks, and bring me a PR." The coordinator writes the brief, dispatches a Codex worker into its own worktree, and returns control immediately. ## Quick Start Ask the coordinator to dispatch an approved task, for example: use Codex to fix the failing login test in my repository, keep scope to the bug, run the existing checks, and bring me a pull request without merging it.

Frequently Asked Questions about sum-dispatch

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

FAQPage Schema
How do I dispatch a coding task to a worker agent?

Write the approved brief to a file and run ./bin/sumctl dispatch with --repo, --brief, and --approved flags. The helper creates a Herdr worktree, launches the selected harness, submits the brief, and registers the pane as that task's worker.

How do I choose which harness or model a worker uses?

Pass --harness, --model, --reasoning, --preset, or --same-as-you at dispatch time. Precedence is explicit instruction, then saved worker default, then the coordinator's own harness, then the harness's native model.

Can a worker agent dispatch its own sub-tasks?

No. Only the pane registered as coordinator by sumctl init can dispatch; the helper refuses dispatch from any other pane. Workers are explicitly given a worker role and cannot claim coordination.

What happens when worker capacity limits are reached?

A refused dispatch names the held slots, and nothing starts. You can park a stopped attempt with execution park to release its reservation, or the user can raise limits with settings set --global; archiving never frees held reservations.

How do I resume a stopped or parked worker attempt?

Use execution resume TASK_ID --attempt ID with the released attempt ID; it checks capacity before launching a successor. Every resume consumes a task repair iteration, including infrastructure relaunches.

What are the limitations of dispatching with uncommitted changes?

Dispatch starts from a committed base and does not copy uncommitted edits from the main checkout. If the main checkout has uncommitted changes, the coordinator explains this before dispatching.