Agent Dispatcher

Coordinate specialized agents across end-to-end feature development workflows.

1|Updated Jul 8, 2016
One-click install
npx skills add https://github.com/oehm-smith/linux-env --skill agent-dispatcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Agent Dispatcher
Source: https://github.com/oehm-smith/linux-env/tree/main/HOME/.claude/skills/crosscutting/process/agent_dispatch
Command: npx skills add https://github.com/oehm-smith/linux-env --skill agent-dispatcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Agent Dispatcher coordinates a set of specialized agents to orchestrate complex feature workflows, enabling multi-step collaboration and consistency across teams.

Core Features & Use Cases

It defines when to invoke each agent (BSA, Architect, Data Engineer, Security Engineer, Tech Writer, QAS, RTE), manages file-based handoffs, and tracks progress through the full lifecycle from requirements to deployment. It supports end-to-end feature workflows, simple feature enhancements, bug fixes, and documentation updates by sequencing the appropriate agents and routing outputs between them.

Quick Start

Start a full seven-agent workflow by initiating BSA analysis and then progress through architecture design, migrations, security audit, implementation, testing, documentation, and release planning.

Frequently Asked Questions about Agent Dispatcher

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

FAQPage Schema
How do I coordinate multiple specialized agents for complex feature development?

Multi-agent coordination for feature development works by determining an agent sequence and routing outputs between specialized roles via file-based handoffs. The dispatcher tracks progress across the full lifecycle from requirements to release.

What is the best way to orchestrate end-to-end workflows across requirements, architecture, and testing?

Orchestrating end-to-end workflows involves sequencing specialized agents like BSA, Architect, and QAS to handle specific phases. The dispatcher manages file-based handoffs to ensure consistency and track overall workflow progress.

How do file-based handoffs work when routing outputs between agents?

File-based handoffs route outputs by having the dispatcher pass files from one specialized agent to the next in the sequence. This ensures each agent receives the exact context needed to continue the feature workflow.

Can I use a multi-agent workflow for simple feature enhancements and bug fixes?

Multi-agent workflows can be used for simple feature enhancements, bug fixes, and documentation updates. The dispatcher sequences the appropriate subset of specialized agents rather than always running the full seven-agent lifecycle.

Which specialized agents are needed for a full feature lifecycle from design to release?

A full feature lifecycle requires specialized agents including BSA, Architect, Data Engineer, Security Engineer, Tech Writer, QAS, and RTE. The dispatcher determines the exact sequence and coordinates handoffs between these roles.

When should I not use a multi-agent dispatch approach for feature development?

A multi-agent dispatch approach should be avoided for isolated tasks that do not require cross-functional handoffs. It is designed for complex feature workflows needing coordination across multiple specialized roles throughout the lifecycle.