orchestration-workflow

Files (1)

• SKILL.md

SKILL.md (first lines)

# Orchestration Workflow: Step-by-Step Guide

Practical walkthrough for using the multi-agent system end-to-end. This is your "how-to" guide for orchestrating features from planning through production deployment.

---

## Your First Feature (Real Example)

**Scenario:** You want to add JWT authentication to your app.  
**Time:** ~6-8 hours total (spread across 1-2 days)  
**Team:** All agents working together  
**Result:** Complete feature with 95% coverage, security audit passed, ready to deploy

---

## Step 1: Plan the Feature (30 minutes)

### What You Do

Open VS Code, start a chat with Copilot:

```
@athena: Plan JWT authentication with refresh tokens

Requirements:
- User login with email + password
- JWT access token (15 min expiry)
- Refresh token (7 day expiry)
- Secure token storage (httpOnly cookies)
- Token verification on protected routes
- Rate limiting (5 attempts/min)
- OWASP Top 10 compliant

Please create a detailed 3-4 phase implementation plan.
```

### What Athena Does

Athena researches patterns, calls Apollo for existing auth code, and creates:

```
📋 Plan: JWT Authentication
├─ Phase 1: Database Schema (Demeter)
│  ├─ Tasks: Create user + token tables
│  ├─ Test requirements: 5 test cases
│  └─ Risk: Zero-downtime migration
├─ Phase 2: Backend Services (Hermes)
│  ├─ Tasks: JWT service + endpoints
│  ├─ Test requirements: 8 test cases
│  └─ Risk: Token expiry edge cases
├─ Phase 3: Frontend Integration (Aphrodite)
│  ├─ Tasks: LoginForm + useAuth hook
│  ├─ Test requirements: 6 test cases
│  └─ Risk: Token refresh race condition
└─ FAQ: Answers to common questions
```

### What You Do

1. Review the plan presented by Athena in chat
2. **Ask questions or approve**
   - If concerns: `@athena: Please adjust plan because...`
   - If approved: "Plan looks good, let's proceed"

### ⏸️ PAUSE POINT 1: Plan Approval

```
Athena: ✅ Plan approved! Ready to orchestrate implementation
Zeus: Starting Phase 1 - Database Schema
```

---

## Step 2: Orchestrate Implementation

### Phase 1: Database Schema

**Zeus delegates to Demeter:**
```
@demeter: Implement database schema for JWT auth

Requirements:
- User table: id, email, hashed_password
- Token table: id, user_id, token, issued_at, expires_at, revoked_at
- Indexes: user(email), token(user_id, token)

TDD: RED → GREEN → REFACTOR
Coverage target: >80%
```

**Demeter does:**
1. Write FAILING migration test (RED)
2. Write minimal migration (GREEN)
3. Refactor (REFACTOR) — add types, indexes, constraints, timestamps

**Demeter delivers:** Schema files + tests, >80% coverage

**Themis reviews:** Coverage, security, performance, tests → APPROVED

**Background dispatch for independent phases (OpenCode v1.16.2+):**
If Phase 2 (backend) and Phase 3 (frontend) have no file dependencies, Zeus can dispatch both in **background** simultaneously and continue working while they execute. This eliminates the sequential wait.

### ⏸️ PAUSE POINT 2: Phase Review

```
Zeus: "Phase 1 complete! Coverage: >80% ✅ Security: ✅ Tests: passing ✅
Ready to continue to Phase 2?"

User: "continue"
```

### Phase 2: Backend Services

**Zeus delegates to Hermes:**
```
@hermes: Implement backend services for JWT auth

Create:
1. JWTService: generate, verify, refresh JWT

From ils15/pantheon-legacy, MIT.

More from ils15/pantheon-legacy