dispatch-authoring

Featured

Write the structured handoff from a planning session to a coding agent: a dispatch with a header, Gate 0 checks, scope, specification, verification, delivery rules, and stop conditions, so the agent can execute unattended and return a reviewable draft PR. Use this skill whenever the user wants to hand work to an agent, write an agent brief, write instructions for Claude Code, Codex, or a Cursor agent, queue work to run overnight, or turn a plan into something an AI coder can execute without asking questions. Triggers on dispatch, hand off to an agent, agent brief, agent handoff, task brief for an AI coder, instructions for Claude Code, Codex task, Cursor agent, background agent, run this overnight, give this to an agent, unattended run. Also triggers when the user has a plan or a spec and asks how to get an agent to build it, even if they never say dispatch.

AI & Automation 1,094 stars 148 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Dispatch Authoring Write the handoff that lets a coding agent execute a plan unattended and come back with something a human can review. Agent-agnostic: works for Claude Code, Codex, or your coding agent of choice. --- ## When to use - Handing a planned change to a coding agent to run without supervision - Queueing work to run overnight or in the background - Turning a spec or a ticket set into an executable brief for an agent - Standardizing handoffs so agent runs are comparable and measurable - Reviewing a draft dispatch before it goes out ## When NOT to use - Writing the spec or PRD the dispatch implements (use `pm-spec-writing`) - Writing the tickets the work is tracked in (use `ticket-authoring`) - Reviewing the PR the agent returns (use `code-review-web`) - Measuring how agent lanes perform over time (use `sprint-operations`) - Pairing interactively with an agent on a small change. A dispatch is for unattended runs. --- ## Required inputs - The plan or spec the agent will implement - The target repository, its visibility (public or private), and its default branch - The repo's own contribution and authoring rules, if any - The commands that prove the work: tests, lint, build, generators - Who merges, and who cleans up afterward If you do not know how the work will be verified, stop and find out. A dispatch without verification is a request for a confident guess. --- ## The framework: 7 parts of a dispatch A dispatch is read top to bottom by an agent with ...

Details

Author
rampstackco
Repository
rampstackco/claude-skills
Created
6 months ago
Last Updated
2 days ago
Language
JavaScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

dispatch

Fan out multiple independent tasks in the current repo to worktree-isolated implementer subagents running in parallel. Each task: implement → auto-detected verification (just/make/gradle/swift/npm/composer/cargo/pytest/dotnet) → commit → push → draft PR (assigned + labeled) → critic review of the diff. One approval gate on the dispatch plan; issue-backed tasks get self-assigned and labeled in-progress. Use when the user has a batch of small-to-medium independent, well-specified tasks (backlog items, issue numbers, cleanup lists) to run in parallel. For a single large feature that needs planning and design judgment, use /orchestrate instead.

0 Updated 2 months ago
tyabu12
AI & Automation Listed

dispatch

Parallelize independent evidence-gathering or audit work into ≥2 concurrent agent tracks; reconcile into a single verdict and action. Also dispatches named agent-box task scripts or ad-hoc prompts to remote <homelab> infrastructure over SSH. Use when sub-tasks are cleanly separable with no output dependencies and running serially wastes turns. Examples: multi-repo scans, concurrent CI/lint/test audits, N-package dependency sweeps. Skip when tasks depend on prior output.

3 Updated 1 weeks ago
LucasSantana-Dev
AI & Automation Listed

dispatch

Parallelize independent evidence-gathering or audit work into ≥2 concurrent agent tracks; reconcile into a single verdict and action. Also dispatches named agent-box task scripts or ad-hoc prompts to remote <homelab> infrastructure over SSH. Use when sub-tasks are cleanly separable with no output dependencies and running serially wastes turns. Examples: multi-repo scans, concurrent CI/lint/test audits, N-package dependency sweeps. Skip when tasks depend on prior output.

2 Updated 2 days ago
LucasSantana-Dev