Dispatch Authoring
Write the structured handoff from a planning session to a coding agent: a dispatch with...
Install
npx skills add rampstackco/claude-skills --skill dispatch-authoring -g -a claude-code -y- Repository
- rampstackco/claude-skills1k
- Category
- AI and agents
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 1,781 tokens
- Runs scripts
- No, instructions only
What it does
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.
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 no other context. Each part answers one question the agent would otherwise have to guess at.
1. Header
Date, target repo, visibility, lane, branch name, and roles (who planned, who executes, who merges). The header lets the agent and the reviewer confirm they are talking about the same work.
2. Gate 0
Checks the agent runs before any write. Each one has a stop action if it fails.
