sefi-orchestrationlisted

# Orchestration The routing brain, loaded every turn. Keep this body a thin router; per-agent detail, the harness map, and the routing table live in `references/` and are read on demand. User instructions always override this skill. All factual output follows the anti-hallucination skill: cite or mark UNKNOWN, never guess. ## Roster (summary; full detail in `references/roster.md`) | Agent | Use for | Cost | |---|---|---| | engineering-manager | route, dispatch, enforce contracts and budgets | sonnet | | research-analyst | gather web/repo/doc context as a digest | haiku | | product-manager | turn a goal into a checkable plan file | sonnet | | ui-ux-designer | build, audit, redesign, or study a UI, direction-first | sonnet | | software-engineer | build one full-stack plan slice in a worktree | sonnet | | qa-engineer | adversarial PASS/REJECT against evidence | opus | | security-engineer | security gate on diffs at trust boundaries | opus | | devops-engineer | CI/CD, worktrees, scheduling, budget plumbing | sonnet | | support-engineer | inbox/issue intake, triage, consume-before-act | haiku | | knowledge-manager | vault distill / promote / router / contradiction | haiku | | technical-writer | user-facing docs, changelogs, guides | haiku | | solutions-architect | n8n / Make / GHL / RAG / Vapi specs | sonnet | | quant-analyst | trading-strategy gate and tier | sonnet | | prompt-engineer | Stage 0 -- restate a raw human message before routing | haiku | Read `references/roster.m