Dispatch

Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.

49 stars 21 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lllyys/vreader --skill dispatch
Manual install
git clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/dispatch ~/.claude/skills/dispatch

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Dispatch (rule 55 — the lane orchestrator)

You are the ORCHESTRATOR. Lanes do the heavy work; you own every contended
surface (trackers, `project.yml`/pbxproj versions, `git tag`, `gh pr`,
docs sync) and all policy decisions. Lanes never decide anything.

## Step 0 — preconditions (any failure ⇒ report, do not dispatch)

1. **Global lock FIRST**: `scripts/agent-lock.sh acquire dispatch` — exit 2
   means another orchestrator (interactive or cron) is mid-batch: report
   "blocked (dispatch busy)" and STOP. Cron prompts take only their
   `cron-<kind>` lock; /dispatch itself owns `dispatch` (pre-acquiring it
   outside would self-deadlock — the lock is non-reentrant).
2. **Kill switch**: if `.claude/state/dispatch-kill` exists → dispatch is
   disabled; run the item(s) through the inline single-item flow
   **while still holding the `dispatch` lock** (the inline flow edits the
   same shared surfaces — running it unlocked could race a concurrent
   batch), release the lock at the end, and say so.
3. **N=1 degrade**: a single work item runs today's inline flow
   (/fix-issue or /feature-workflow) — fan-out overhead isn't worth it
   (rule 48 decision test). Same rule: **the inline degrade runs under the
   `dispatch` lock**, released when the inline flow finishes.
4. **Width**: default 1 lane; open a second ONLY with memory headroom —
   check `vm_stat` free+inactive pages ≳ 4GB equivalent. Hard cap 2.
   `android-app`/`android-spike` items always width 1 (no ANDROID_SERIAL
Read the full skill on GitHub

Details

Skill name
dispatch
Repository
lllyys/vreader
Path
.claude/skills/dispatch/SKILL.md
Repo updated
6 August 2026

FAQ

What does the Dispatch skill do?

Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.

How do I install the Dispatch skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill dispatch. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dispatch popular?

It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.

Related skills

AI Coding Agents

49

lllyys/vreader

Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.

AI, LLMs & Agents21

Feature Workflow

49

lllyys/vreader

Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud

Productivity & Notes21

File Bug

49

lllyys/vreader

Create a GitHub issue for a bug row in docs/bugs.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing bug row, or asks 'create issue for bug #N', 'file bug 115', 'mirror bug 42 to GH', 'this bug needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/bugs.md` row because it lacks `GH: #N`. Stays strictly in the mirror-an-existing-row scope — do not use for triaging new bugs (that's the triage skill) or fixing bugs (that's fix-issue).

Writing & Content21

Dsv41 Scheduler Benchmark

49

hw-native-sys/simpler

Run and compare DeepSeek V4.1 Flash decode scheduler benchmarks on Ascend A5. Use for pypto-lib dev branches or daily CI performance cases, Simpler tests/fdwic/dsv41_scheduler, A5 HBG no-graph baselines, runtime A/B or stacked-PR comparisons, and L1/L3 traces for these cases.

Git & Code Review102

Create Issue

49

hw-native-sys/simpler

Create a GitHub issue following the project's issue templates. Classifies the issue type, fills required fields per template, and creates it via gh CLI. Use when the user wants to file a bug, request a feature, or create any GitHub issue.

Git & Code Review102

Fix Issue

49

hw-native-sys/simpler

Implement a GitHub Issue as its assignee or delegated contributor, selecting direct repair or develop-task planning and following through to a reviewed PR. Use when asked to fix or work on an Issue; use process-issue for maintainer triage.

Git & Code Review102

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.