dispatch-ready

Dispatches Ready GitHub issues to sub-agents in idempotent loop ticks with concurrency caps.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill dispatch-ready-sassy-dog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch-ready
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/dispatch-ready
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill dispatch-ready-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a groomed backlog by hand means repeatedly checking which PRs are green, which issues are free to start, and how many agents are already running. This Skill automates that loop: each invocation reconciles in-flight PRs, computes remaining capacity, and dispatches new work only from issues marked Ready. ## Core Features & Use Cases - Idempotent tick loop: Each run reconciles in-flight PRs (merge-ready, failed, conflicting, blocked) against live GitHub state, then tops the pipeline up to the configured max_in_flight limit. - Ready-only selection with filters: Pulls exclusively from Ready issues, skipping claimed, blocked, site-mismatched, dependency-blocked, and file-collision candidates, with stack-aware exemptions. - Failure and recovery accounting: Tracks a single shared recovery allowance per PR via authenticated issue comments, demotes repeat failures and conflicting PRs to blocked, and never parks failures back in Ready. - Use Case: Run it under /loop 5m to continuously drain a repo's Ready queue — it merges green PRs via pr-shepherd, dispatches one worktree sub-agent per new issue, and stops at a terminal state when the queue empties or stalls. ## Quick Start Ask the agent to work the ready queue by saying "dispatch ready items in the backlog" after configuring the repo with setup-config.

Frequently Asked Questions about dispatch-ready

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

FAQPage Schema
How do I automatically work through a GitHub backlog of ready issues?

Run dispatch-ready under a loop such as /loop 5m. Each invocation reconciles in-flight PRs first, computes free capacity from max_in_flight, then dispatches sub-agents only for issues marked Ready that pass dependency, collision, and site filters.

What happens when a dispatched pull request fails CI checks?

The tick reports the failing check and comments the failure on the issue. One redispatch with failure context is allowed on a later tick; a second failure demotes the issue to blocked with an explanatory comment, and a human decides next steps.

Can dispatch-ready run without a repo configuration file?

No. If .claude/sassy-dog/dispatch-ready.md is missing, the skill stops and directs you to run setup-config first, because dispatching unattended without a concurrency cap or migration sequencing rules is unsafe.

Does dispatch-ready handle conflicting pull requests automatically?

No. A CONFLICTING PR is demoted on sight: the issue gets a blocked label and a comment explaining a human must rebase. The loop never auto-rebases, and clearing the blocked label after rebasing returns the issue to the queue.

How does dispatch-ready avoid dispatching issues that conflict with in-flight work?

It compares each candidate's declared touches file set against the actual changed files of open PRs from in-flight and blocked issues. Overlapping issues are deferred to a later tick, and issues with no touches annotation are flagged in the tick report.