Menu
Multi-agent orchestration with model routing, category delegation, and sprint management. Use for coordinating Pantheon agents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Tool-agnostic search — query construction, tool selection, source trust hierarchy.
Auto-continue through todos with idle detection and safety gates. Use for multi-step orchestration.
Level 2 — Pantheon-native context compression with priority scoring, semantic summarization, downstream-aware compression, budget allocation, and cross-references
Automated visual review pipeline — Playwright screenshots, self-analysis, fix loop, escalation. Used by Aphrodite for UI verification.
MCP security hardening — credential leakage prevention, input sanitization, and tool access control. Use for reviewing agent MCP configurations.
Load prompts from external files with path expansion. Use for version-controlled prompts outside config.
| name | agent-coordination |
| description | Multi-agent orchestration with model routing, category delegation, and sprint management. Use for coordinating Pantheon agents. |
| context | fork |
| globs | [] |
| alwaysApply | false |
Master guide to orchestrating the multi-agent system. Includes category routing, model selection, and sprint management for rapid, TDD-driven feature development.
See AGENTS.md for the full agent table.
Route tasks to optimized agents based on category instead of specifying agents manually:
| Category | Agent | Use For |
|---|---|---|
| Deep | Athena, Hephaestus | Complex planning, AI pipelines |
| Quick | Talos, Apollo | Fast fixes, codebase search |
| Ultrabrain | Zeus | Multi-agent orchestration, model routing |
1. User describes feature
2. @athena creates PLAN with phases and agents
3. User approves PLAN (GATE 1)
4. Zeus dispatches agents to phases (parallel when possible)
5. Each agent: TDD cycle → writes IMPL artifact
6. @themis reviews all phases (GATE 2)
7. User reviews Themis findings
8. If approved → user commits (GATE 3)
9. @mnemosyne updates memory bank
🔀 PARALLEL EXECUTION — Phase 2
Running simultaneously:
- @hermes → backend tests → .tmp/IMPL-phase2-hermes.md
- @aphrodite → frontend → .tmp/IMPL-phase2-aphrodite.md
- @demeter → migrations → .tmp/IMPL-phase2-demeter.md
Themis reviews all three after completion.
All phase outputs go to .pantheon/memory-bank/.tmp/. See skill: artifact-management for the complete protocol (who generates what, templates, lifecycle).
| Gate | When | Why |
|---|---|---|
| GATE 1 | After PLAN | User confirms scope |
| GATE 2 | After Themis review | User sees changes |
| GATE 3 | Before git commit | User controls history |
Model routing is handled by Prometheus and the platform configuration. Zeus delegates model selection to the tier system (fast / default / coding / premium).