orchestrator
Orchestrator - Multi-Agent Parallel Execution
Spawn autonomous workers to execute tracks in parallel using Agent Mail coordination.
Agent Mail: CLI Primary, MCP Fallback
This skill uses a lazy-load pattern for Agent Mail:
| Priority | Tool | When Available |
|---|---|---|
| Primary | bun toolboxes/agent-mail/agent-mail.js |
Always (via Bash) |
| Fallback | MCP tools (via mcp.json) |
When skill loaded + MCP server running |
Detection flow:
1. Try CLI: bun toolboxes/agent-mail/agent-mail.js health-check
↓ success? → Use CLI for all Agent Mail operations
↓ fails?
2. Fallback: MCP tools (lazy-loaded via skills/orchestrator/mcp.json)
More from reinamaccredy/maestro
conductor
Implementation execution for context-driven development. Trigger with ci, /conductor-implement, or /conductor-* commands. Use when executing tracks with specs/plans. For design phases, see designing skill. For session handoffs, see handoff skill.
10maestro-revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
9maestro-new-track
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
8init
Generates AGENTS.md and CLAUDE.md files using the WHAT/WHY/HOW framework. Explores the codebase and produces minimal (<100 line) context files with progressive disclosure.
8maestro-setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
7tracking
>
7