Retired: the autonomous dispatch tick is now the headless dispatch-tick script (launched by dispatch-spawn-tick); see the dispatch terminal command for the manual entry point.
Installs into .claude/skills of the current project.
Are you the author of Dispatch Propagate?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/natb1-dispatch-propagate)
---
name: dispatch-propagate
description: "Retired: the autonomous dispatch tick is now the headless dispatch-tick script (launched by dispatch-spawn-tick); see the dispatch terminal command for the manual entry point."
---
# Dispatch (propagate) — retired
The autonomous dispatch tick no longer runs as a model session. It is the
headless `.claude/skills/dispatch-propagate/scripts/dispatch-tick` script, which
runs `dispatch-select-tick` then `dispatch-materialize-spawn` with no
model-decision seam.
`dispatch-spawn-tick` launches that script as a transient `systemd-run --user`
unit. The worker Stop-hook (`.claude/hooks/dispatch-stop.sh`) and the reseed
timers (`dispatch-schedule-reseed`, `dispatch-schedule-target-reseed`) drive the
chain by calling `dispatch-spawn-tick` — there is no per-tick `claude --bg`
router session anymore. Model sessions exist only for workers (the phase skills
doing real judgment).
The routing this skill used to document — selecting the target, gating on the
concurrency budget, materializing the worktree, and spawning the worker — now
lives in the `dispatch-tick` script header and in `reference.md`.
A human runs the `dispatch` terminal command (bare, or `dispatch <N>`) to invoke one
tick from a terminal; its stdout streams directly.
