# prime-orchestration

> Use this when orchestrating multi-agent workflows, delegating tasks, or coordinating between Prime agents. Contains routing patterns, delegation rules, and agent coordination protocols.

- Author: ElementofPrime
- Repository: ElementofPrime/eop-agentics
- Version: 20260206013214
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/ElementofPrime/eop-agentics
- Web: https://mule.run/skillshub/@@ElementofPrime/eop-agentics~prime-orchestration:20260206013214

---

---
name: prime-orchestration
description: Use this when orchestrating multi-agent workflows, delegating tasks, or coordinating between Prime agents. Contains routing patterns, delegation rules, and agent coordination protocols.
---

## Use this when

- Deciding which agent to delegate a task to
- Coordinating multiple agents on a project
- Managing the Prime Forge workflow phases
- Routing research or build tasks

## Agent Roster

### Core Agents

| Agent | Model | Specialty | When to Use |
|-------|-------|-----------|-------------|
| **Prime** | claude-opus-4-5 | Orchestration | Never codes, only coordinates |
| **Forge** | gpt-5.2-codex | Building | All coding/implementation |
| **Scout** | claude-haiku-4-5 | Fast explore | Quick lookups, file finding |
| **Archivist** | claude-sonnet-4 | Deep research | Thorough analysis, patterns |
| **Sentinel** | gemini-3-pro | External intel | Docs, APIs, web research |

### Extended Agents (Phase 2)

| Agent | Model | Specialty |
|-------|-------|-----------|
| **Herald** | grok-3 | Social/X trends, real-time news |
| **Analyst** | gemini-3-pro | Market/competitive analysis |
| **Compass** | claude-opus-4-5-thinking | Deep strategic planning |

## Workflow Phases

```
IDEA ──► BRAINSTORM ──► APPROVAL ──► INTEL ──► APPROVAL
              │                         │
        (Prime+Jeremy)            (Specialists)
                                        │
                                        ▼
        DONE ◄── REVIEW ◄── BUILD ◄── SPEC-KIT ◄── APPROVAL
          │          │          │
    (Prime Stamp)  (Loop)   (Forge)
```

## Delegation Patterns

### Research Tasks
```
Fast lookup → Scout
Deep analysis → Archivist
External docs → Sentinel
Social/trends → Herald
Market intel → Analyst
```

### Build Tasks
```
All coding → Forge
Pattern finding → Scout (support)
Verification → Archivist (support)
```

### Strategic Tasks
```
Planning → Prime + Compass
Decisions → Prime + Jeremy (approval)
```

## Agent Coordination Syntax

### Single Agent
```
@forge: Implement the login form per spec
```

### Parallel Agents
```
PARALLEL:
  @scout: Find auth patterns in codebase
  @sentinel: Fetch OAuth2 best practices
  @archivist: Analyze existing user model
THEN:
  @forge: Implement auth using findings
```

### Agent Debate
```
DEBATE:
  @archivist: Present research on approach A
  @sentinel: Present research on approach B
SYNTHESIZE:
  @prime: Combine findings, present to Jeremy
```

## Routing Rules

1. **Never bypass Prime** for final decisions
2. **Never let Forge decide** architecture - ask Prime
3. **Always parallel** when tasks are independent
4. **Always sequential** when tasks depend on each other
5. **Always debate** when there are multiple valid approaches

## Approval Protocol

Every phase transition requires:
1. Agent work complete
2. Prime review
3. Jeremy approval

Options at each checkpoint:
- **APPROVE** - Move to next phase
- **REFINE** - Loop back with feedback
- **RETHINK** - Major pivot needed
- **QUESTIONS** - Clarification before deciding

## Quick Reference

```
/prime.brainstorm → Ideation with Prime+Jeremy
/prime.intel      → Delegate to research agents
/prime.spec       → Create spec-kit
/prime.build      → Orchestrate Forge
/prime.review     → Final quality gate
```