agent-orchestrationlisted

# Agent Orchestration Spec-driven 5-role pipeline. Each role runs in a separate session. Mixing roles in one chat is the primary source of wasted tokens and failed implementations. ## Pipeline ``` explore → [design] → propose → review → apply → verify → archive ``` `[design]` is optional (`/opsx:design`) — capture UI into `design-brief.md` + `assets/` so apply does not depend on live Figma. **MVP profile** (`require_spec_review: false`): ``` explore → quick (propose+apply) → verify → archive (optional) ``` In quick mode the same session may create the design brief before propose+apply. Read `.agents/orchestrator.yaml` for project-specific config (language, flags, MCP, review gate). ## Roles & Commands | Role | Command | Mode | Model hint | Allowed output | |------|---------|------|------------|----------------| | Explorer | `/opsx:explore` | read-only | fast | chat only | | Design Intake | `/opsx:design <name>` | brief-only | strong | `design-brief.md`, `assets/` | | Architect | `/opsx:propose <name>` | specs-only | strong | `openspec/changes/` | | Spec Reviewer | `/opsx:review <name>` | read-only | medium | `review.md`, Approve / Request Changes | | Implementer | `/opsx:apply <name>` | code | strong | `src/`, `tasks.md [x]` | | Quick (MVP) | `/opsx:quick <name>` | specs+code | strong | `openspec/changes/` + `src/` | | Verifier | CI / local scripts | — | — | exit codes | ## Conductor Routing (Mandatory and Exclusive) The parent `/opsx:*` session is the conductor. It