workflow-orchestrator
55·
Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code
today
barkainBy emasoft
Task distribution, agent coordination, progress monitoring - executes plans via subagents. Requires AI Maestro for inter-agent messaging.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-orchestrator-agentAdd a new module during Orchestration Phase (dynamic flexibility)
Assign a module to a registered agent with Instruction Verification Protocol
Cancel active orchestrator loop
Poll all active remote agents for progress with MANDATORY questions
Generate a comprehensive handoff document for a replacement agent
Modify a module's specifications during Orchestration Phase
Display Orchestration Phase progress - module completion, assignments, verification status
Start orchestrator loop - monitors tasks across Claude Tasks, GitHub, task files
Check orchestrator loop status and pending tasks
Change a module's priority level
Reassign GitHub Project kanban tasks from one agent to another
Reassign a module to a different agent
Register a remote agent (AI or human) for module assignment
Remove a pending module from Orchestration Phase (only if not started)
Enter Orchestration Phase - begin coordinating remote agents for implementation
Compiles verification checklists from requirements and specifications. Requires AI Maestro installed.
Manages Docker containers for cross-platform development and isolated testing. Requires AI Maestro installed.
Experimental validation agent - the ONLY local agent authorized to write code. Requires AI Maestro installed.
Orchestrator main agent - task distribution, kanban management, agent coordination. Requires AI Maestro installed.
Summarizes verbose task outputs into minimal reports for orchestrator consumption. Requires AI Maestro installed.
Coordinates multiple developer agents working in parallel on features using GitHub Projects and AI Maestro messaging for task management and team coordination. Requires AI Maestro installed.
Use when replacing agents. Trigger with agent replacement or handoff requests.
Use when compiling verification checklists from requirements including module completion, quality gates, and test coverage checklists. Trigger with checklist compilation requests.
Trigger with developer communication needs. Use when communicating with human developers in code reviews, issues, technical discussions, and status updates. Covers effective communication patterns.
Trigger with Claude Code action requests. Use when setting up Claude Code in GitHub Actions for automated PR reviews, @claude mention responses, and issue triage.
Interview protocols for task verification. Use when checking implementer readiness or approving PR creation. Trigger with task assignment.
GitHub Projects V2 kanban board management. Use when creating boards, adding columns, moving items. Trigger with kanban or column requests.
GitHub label taxonomy for multi-agent systems. Use when managing labels for issue tracking and coordination. Trigger with label requests.
AI Maestro message templates for emasoft plugins. Use when sending task assignments, status reports, or escalations between agents. Trigger with messaging requests.
Trigger with module management tasks. Use when managing modules during Orchestration Phase (add, modify, remove, prioritize, reassign). Every module maps 1:1 to GitHub Issue.
Use when managing orchestration phase commands. Trigger with start, monitor, loop control, cancellation, or stop hook enforcement requests.
Use when coordinating work among multiple developers. Trigger with orchestration requests.
Agent progress monitoring via state-based detection. Use when tracking task completion, detecting stalls, or escalating unresponsive agents. Trigger with progress checks.
Use when coordinating remote AI agents. Trigger with task delegation or multi-agent coordination requests.
Task distribution based on skills and availability. Use when assigning work to agents, balancing load, or resolving dependencies. Trigger with assignment requests.
Use when orchestrating complex projects. Trigger with multi-module or two-phase planning requests.
Use when verifying implementations. Trigger with verification, testing, or evidence requests.
Version: 1.0.0
The Orchestrator Agent handles task distribution, agent coordination, and progress monitoring. It receives plans from the Architect and coordinates subagents to implement them.
| Agent | Description |
|---|---|
eoa-main.md | Main orchestrator agent |
eoa-team-orchestrator.md | Coordinates team of agents |
eoa-task-summarizer.md | Summarizes task progress |
eoa-checklist-compiler.md | Creates verification checklists |
eoa-docker-container-expert.md | Docker and container expertise |
eoa-experimenter.md | Experimentation and prototyping |
| Command | Description |
|---|---|
eoa-start-orchestration | Start orchestration phase |
eoa-register-agent | Register remote agent |
eoa-assign-module | Assign module to agent |
eoa-reassign-module | Reassign module |
eoa-check-agents | Check agent status |
eoa-add-module | Add new module |
eoa-modify-module | Modify module |
eoa-remove-module | Remove module |
eoa-prioritize-module | Change module priority |
eoa-orchestrator-loop | Start orchestration loop |
eoa-orchestrator-status | Check orchestrator status |
eoa-cancel-orchestrator | Cancel orchestration |
| Skill | Description |
|---|---|
eoa-two-phase-mode | Two-phase orchestration mode |
eoa-orchestration-commands | Orchestration command patterns |
eoa-orchestration-patterns | Orchestration best practices |
eoa-remote-agent-coordinator | Remote agent coordination |
eoa-module-management | Module CRUD operations |
eoa-verification-patterns | Instruction verification |
eoa-developer-communication | Developer comm patterns |
eoa-checklist-compilation-patterns | Checklist generation |
eoa-agent-replacement | Agent replacement handoffs |
eoa-task-distribution | Task breakdown and assignment |
eoa-progress-monitoring | Progress tracking and polling |
eoa-messaging-templates | AI Maestro message formats |
eoa-label-taxonomy | GitHub label system |
eoa-implementer-interview-protocol | Interview-based requirements |
eoa-github-action-integration | GitHub Actions patterns |
| Hook | Event | Description |
|---|---|---|
eoa-orchestrator-stop | Stop | Block exit until tasks complete |
eoa-instruction-verification-check | PreToolUse | Verify instructions before work |
eoa-polling-reminder | UserPromptSubmit | Remind to poll progress |
eoa-file-tracker | PostToolUse | Track file modifications |
Install from the Emasoft marketplace. Use --scope local to install only for this agent's directory only, or --scope global for all projects.
Role plugins are installed with --scope local inside the specific agent's working directory (~/agents/<agent-name>/). This ensures the plugin is only available to that agent.
# Add Emasoft marketplace (first time only)
claude plugin marketplace add emasoft-plugins --url https://github.com/Emasoft/emasoft-plugins
# Install plugin (--scope local = this agent's directory only, recommended)
claude plugin install emasoft-orchestrator-agent@emasoft-plugins --scope local
# RESTART Claude Code after installing (required!)
Once installed, start a session with the main agent:
claude --agent eoa-orchestrator-main-agent
--plugin-dir loads a plugin directly from a local directory without marketplace installation. Use only during plugin development.
claude --plugin-dir ./OUTPUT_SKILLS/emasoft-orchestrator-agent
cd OUTPUT_SKILLS/emasoft-orchestrator-agent
uv run python scripts/validate_plugin.py . --verbose
Task distribution, agent coordination, progress monitoring - executes plans via subagents. Requires AI Maestro for inter-agent messaging.
Multi-agent orchestrator — supervisor loop that launches agents to implement plans
Skills for AI agent orchestration - memory search, code graph queries, documentation search, inter-agent messaging, and task planning
This skill should be used when the model's ROLE_TYPE is orchestrator and needs to delegate tasks to specialist sub-agents. Provides scientific delegation framework ensuring world-building context (WHERE, WHAT, WHY) while preserving agent autonomy in implementation decisions (HOW). Use when planning task delegation, structuring sub-agent prompts, or coordinating multi-agent workflows.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code
barkainMulti-agent orchestration with AI SDK v5 - handoffs, routing, and coordination for any AI provider (OpenAI, Anthropic, Google)
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim