dispatch-task

Plans a task type then dispatches implementation to agents in parallel git worktrees.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill dispatch-task-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dispatch-task
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/dispatch-task
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill dispatch-task-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-agent software work requires both upfront planning (RFCs, BRDs, ADRs, triage reports, board tasks) and isolated parallel execution; doing these by hand risks agents working from missing docs, conflicting branches, or unapproved plans. ## Core Features & Use Cases - Two-phase orchestration: Runs the full planning chain for new-feature, tech-task, investigate-bug, or investigate-crash in a single planning worktree, then blocks on explicit user approval before dispatching. - Parallel worktree dispatch: Creates one git worktree per implementation task from the resolved base branch and hands off to specialized agents in parallel with a mandatory setup preamble. - Artifact landing gate: Commits and merges Phase 1 docs and board tasks to the base branch, then verifies every doc and task exists on origin before any worktree is cut. - Use Case: Say you want to add a checkout feature spanning Android, iOS, and backend. Run /dispatch-task --type new-feature "checkout flow" to produce the RFC/BRD/ADR, create board tasks, and after approval dispatch three agents into isolated worktrees that each open PRs back to the base branch. ## Quick Start Ask the AI to run /dispatch-task --type new-feature with a short description of the feature you want planned and implemented in parallel.

Frequently Asked Questions about dispatch-task

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

FAQPage Schema
How do I plan a feature and parallelize its implementation across agents?▼

Run /dispatch-task --type new-feature with a description. It runs the planning chain (RFC, BRD, ADR as size dictates), creates board tasks, waits for your approval, then creates one git worktree per task and dispatches agents in parallel.

What is the difference between /dispatch-task and /dispatch?▼

/dispatch-task adds a full planning phase with docs, board tasks, and an approval gate before parallelizing. /dispatch is raw worktree parallelization with no planning, used when docs are already approved and tasks are on the board.

Why must planning docs be merged before worktrees are created?▼

Phase 2 cuts every worktree from origin/$BASE, so uncommitted docs and board tasks are invisible to dispatched agents. The skill commits Phase 1 artifacts, merges them via PR, and verifies each doc and task exists on the base branch before dispatching.

Can I dispatch bug or crash investigations with this skill?▼

Yes. Use --type investigate-bug or investigate-crash. The skill produces a triage report with root cause, culprit commit, severity, and fix recommendation, then dispatches the fix and prevention tasks to the relevant domain agents.

When should I not use /dispatch-task?▼

Skip it for pure planning without implementation, already-planned work (use /dispatch), single sequential tasks, tasks with hard dependencies on each other, and trivial one-line fixes that do not need worktree overhead.