dispatch

Standardize worktree subagent prompt dispatch with mandatory framing and verification gates.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill dispatch-azigler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/dispatch
Command: npx skills add https://github.com/azigler/dotfiles --skill dispatch-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents orchestrator-driven prompt drift by providing a consistent, guardrailed template for worktree subagent dispatches, ensuring critical instructions (like no nested agents and correct merge targets) are never omitted.

Core Features & Use Cases

  • Canonical dispatch prompt skeleton: Frames every subagent with the same mandatory blocks to reduce variance across runs and sessions.
  • Safety/guardrails for worktree hygiene: Enforces “no nested agents” and constrains file paths to the subagent worktree to protect orchestrator git-state accuracy.
  • Wave-aware context and verification gates: Includes wave-position context (when applicable) plus acceptance criteria and pre-commit verification expectations.
  • Type-specific add-ons: Adds required sections for test/spec/check/fix/scrutinize/impl variants so each subagent type behaves correctly.

Quick Start

Use the dispatch skill right before every worktree subagent dispatch so the subagent prompt is rendered with the correct bead ID, merge target, and required verification gates.

Frequently Asked Questions about dispatch

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

FAQPage Schema
How do I prevent orchestrator drift when dispatching subagents across multiple sessions?

To prevent orchestrator drift, use a standardized worktree subagent prompt template that enforces mandatory framing, prohibits nested agent spawning, and includes acceptance criteria for every dispatch.

Why does my git worktree flow break when subagents modify files outside their assigned directory?

Git worktree flows break when subagents modify files outside their worktree because it compromises orchestrator git-state accuracy, which is why worktree-bounded file path constraints are necessary.

How do I standardize subagent prompts for wave-based git workflows?

Standardize subagent prompts for wave-based workflows by applying a canonical dispatch skeleton that includes wave-position context, merge-target constraints, and pre-commit verification expectations.

Can I use a single prompt template for different subagent types like test, fix, and impl?

Yes, a single dispatch template can support different subagent types by injecting type-specific add-ons so each test, fix, spec, check, scrutinize, or impl variant receives the correct required sections.

What happens if a subagent spawns another nested agent during a worktree dispatch?

If a subagent spawns a nested agent, it violates the safety guardrails designed to protect git hygiene and orchestrator state accuracy, which is why nested agent spawning is explicitly prohibited.