dispatch-helperslisted

Use whenever the orchestrator is about to issue a raw Agent() / Task() dispatch to a devt:* subagent (single OR parallel) instead of routing through /devt:review or /devt:workflow. Surfaces two CLIs that build the canonical envelope so context blocks (scope_trust, scope_hint, memory_signal, governing_rules) are never silently dropped — `dispatch run agent --task=...` for one-off single dispatches, `dispatch render-filled agent:auto` for advanced cases (lane fan-out, pre-computation, custom edits). Trigger phrases include single dispatches like "dispatch devt:code-reviewer to review X", "run devt:programmer for Y"; fan-out like "fan out review across files", "parallel reviewer across communities"; recovery like "re-dispatch programmer with continuation".
emrecdr/devt · ★ 0 · AI & Automation · score 75

Install: claude install-skill emrecdr/devt

# Dispatch Helpers — Canonical Envelope Generation for Raw Dispatches ## When to use this skill The devt CLAUDE.md "Critical Agent + Workflow Contracts" section says: > Never raw-dispatch devt agents. Orchestrators MUST route through devt slash commands (/devt:review, /devt:workflow, …). Direct Task(subagent_type="devt:*", prompt=…) calls bypass the workflow's dispatch template — losing <scope_trust>, <scope_hint>, <memory_signal>, the graph-impact map injection, the impact-plan, the verifier loop, and the telemetry surface. **Prefer `/devt:review` / `/devt:workflow` / `/devt:debug` when applicable.** This skill is for the genuine edge cases where the canonical path doesn't fit: ad-hoc single dispatches that don't match a slash command's shape, parallel fan-out across file groups, or recovery / second-pass scenarios on existing artifacts. The cost of bypassing canonical paths without this skill: orchestrators construct prose context by hand, drop the structured blocks, and the agent runs in degraded mode (grep-first discovery, no caller verification, no telemetry). The CLIs below eliminate that cost. ## CLI surface — pick by shape ### One-off dispatch (the common case) — `dispatch run` Use for ONE devt agent invocation that doesn't fit a `/devt:*` slash command. Example: dispatching `devt:tester` to rewrite a hurl spec file when no slash command matches that intent. ```bash node "${CLAUDE_PLUGIN_ROOT}/bin/devt-tools.cjs" dispatch run <agent> --task="..." ``` - `<age