Agent skill · operations · jeremylongshore

dispatch

Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it", "run the batches".

Why this skill is useful

Adds a complex orchestration workflow with parallel processing and multi-level review mechanisms that are not commonly found in standard documentation.

What it needs

Requires bash installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Dispatch Workhorse phase. Picks up a task file from /hyperflow:plan and runs it through the orchestrator pattern with parallel worker dispatch and multi-level reviews. This skill exercises Layer 3 (Orchestrator), Layer 5 (Quality Gates), Layer 6 (Project Memory), Layer 8 (Git Workflow), and Layer 9 (Security) from the doctrine. Multi-level review (L1–L5) is applied per the triage's flow profile. Per-Step Agent Map (DOCTRINE rule 12 — §12.1 inline-allowed for trivial steps · §12.2 sub-phase decomposition) Every substantive step dispatches at least one Agent. Trivial steps (≤ 2 tool calls, no content generation, no decision-making, mechanically verifiable) MAY be performed inline by the orchestrator per §12.1. Non-trivial steps decompose into ≥ 2 named sub-phases per §12.2. Step Sub-phase Workers Reviewer Notes --- --- --- --- --- 0 — Mode confirm — (exempt) — — AskUserQuestion only 0.5 — Operational choices — (exempt) — — AskUserQuestion only 1 — Load task — (atomic · §12.2.8) — — Read + schema check = single mechanical decision; no parallel angles 2a — Pre-dispatch Composer × N parallel — one per sub-task; stitches persona + injects learnings Reviewer — reviews prompt set for completeness Parallel worker prompts built before any fan-out fires 2b — Worker fan-out Implementer / Searcher / Writer × N parallel Domain specialist Reviewer — the Specialist:-matched agent, batched over full batch (P2) or per-sub-task fallback One Reviewer call per batch; security/correctness specialists run with --thorough 2c — Gate run Worker — runs lint/typecheck/tests on affected files Reviewer — judges gate output Small focused diff 2d — Learnings + commit Writer — synthesizes per-batch learnings — (mechanical commit · §12.1) Per-sub-task PASS commits land here; learnings appended to context 3 — Final integration review — (atomic · §12.2.8) Reviewer — broadest matching specialist(s), L1–L<n> over full diff Single Reviewer dispatch; skipped under D7 incl. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/dispatch

View the source on GitHub

Browse the @skills marketplace