dispatch

Orchestrate repository goal queues into claim, verify, and merge workflows.

4|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/pragmaticgrowth/flywheel --skill dispatch-pragmaticgrowth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch
Source: https://github.com/pragmaticgrowth/flywheel/tree/main/skills/dispatch
Command: npx skills add https://github.com/pragmaticgrowth/flywheel --skill dispatch-pragmaticgrowth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Dispatch turns a repository-backed goals queue into controlled autonomous execution, so agents can claim work, verify it, and shepherd it through completion without losing track of state or safety.

Core Features & Use Cases

  • Queue orchestration: Reads docs/goals/index.yaml, claims ready goals, and keeps work slots filled according to priority, dependencies, and WIP limits.
  • Agent lifecycle management: Spawns isolated implementer agents, detects stale or blocked work, and respawns or escalates when necessary.
  • Verification and integration: Runs deterministic validation, optional LLM validation, and safe merge workflows before marking goals complete.
  • Use Case: A team wants unattended delivery for a backlog of repository goals, with each goal tracked in Git, verified against acceptance criteria, and merged only after passing the required gates.

Quick Start

Ask the assistant to dispatch the next queued goal in the repository and keep working until the goal is verified, merged, and marked complete.

Frequently Asked Questions about dispatch

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

FAQPage Schema
How do I automate pull request workflows from a git-backed goal queue?

Automating pull request workflows from a git-backed goal queue requires parsing goal indices, tracking branch states, and running deterministic validation before guarded merges. This Skill orchestrates that lifecycle from claim to merge.

What is the best way to manage autonomous agent spawning for repository goals?

Managing autonomous agent spawning for repository goals involves reading docs/goals/index.yaml, claiming ready goals, and spawning isolated implementer agents within WIP limits. This Skill handles lifecycle management and escalates blocked work.

How do I set up unattended delivery for a backlog of repository goals?

Unattended delivery for a backlog of repository goals starts by asking the assistant to dispatch the next queued goal and keep working until it is verified, merged, and marked complete.

Does dispatch work with docs/goals-driven execution for repeated PR shepherding?

Yes, dispatch applies to docs/goals-driven execution in repos that need repeated PR shepherding. It tracks branch and PR states, applies deterministic validation, and handles guarded merges.

How does queue orchestration handle stale or blocked git work?

Queue orchestration handles stale or blocked git work by detecting stalled states during agent lifecycle management and respawning or escalating work as necessary to keep goal slots filled.

When should I not use autonomous goal queue orchestration?

You should not use autonomous goal queue orchestration when goals lack acceptance criteria or deterministic validation gates, because guarded merges depend on passing required verification steps.