🎛️ Phase 2 — Wiring specialists into firing surfaces
Goal: convert dormant specialist agents into ones that actually spawn. Method: a 6-agent adversarial proposal workflow — propose a real subagent_type= spawn per mis-triggered agent, then skeptically verify it's not a forced/cosmetic fit. Forcing a spawn that never fires is worse than leaving the agent dormant.
1
wired (real firing surface)
2
deferred (need new spawn surface)
3
dropped (forced / already wired)
5/6
NOT force-wired — by design
Per-agent disposition
| Agent | Verdict | Why |
|---|
| event-driven-architect | WIRED ✅ | Clean home: conditional Agent 5 in implement/references/agent-phases.md Phase 4 (the REAL spawn block), guarded by event/CQRS/queue feature shape. Self-justifies like the LLM agent. |
| monitoring-engineer | DEFER | Natural home is devops-deployment observability — but that skill spawns NOTHING today (guidance-only). Wiring needs a new spawn surface; design decision deferred. |
| git-operations-engineer | DEFER | create-pr's agent surface (parallel-validation.md) is for diff validation; its git handling is deterministic bash. Git-ops here would be a forced fit. |
| security-layer-auditor | DROP | Already wired — it's in implement/references/agent-teams-security-audit.md (Phase 4/6 mesh team). Not actually dormant in the wiring sense; a second spawn would duplicate. |
| component-curator | DROP | Only fit (design-to-code) is MCP-gated + not high-traffic, and a fire-and-forget pre-pass feeding a synchronous gated stage is an async/sync mismatch — wouldn't meaningfully fire. |
| design-system-architect | DROP | The design-to-code "no token system" trigger is the greenfield single-component case — spawning a heavyweight 3-tier OKLCH foundation there derails the task. Contrived. |
The one real wire
✅ event-driven-architect lands in the firing surface (agent-phases.md), not the descriptive SKILL.md table. The verifier caught that a SKILL.md-prose edit "would never fire" — the actual Agent(subagent_type=...) calls live in references/agent-phases.md. This is the whole-session discipline: does it actually fire?
### Agent 5: Event-Driven Architect (conditional)
Spawn ONLY when the feature is event-sourcing / CQRS / message-queue / outbox-shaped.
Agent(
subagent_type="ork:event-driven-architect",
model=MODEL_OVERRIDE,
prompt="""... First decide: is this feature event-driven-shaped? (justify yes/no) ...""",
run_in_background=true
)
The honest finding
⚠️ Phase 2's real surface is narrower than "wire all 6." Most "mis-triggered" agents are either already-wired (security-layer), async-incompatible (component-curator), or would need a brand-new spawn surface introduced into a guidance skill (monitoring, git-ops, design-system). The adversarial pass prevented 5 cosmetic wires. The remaining activation lever is Phase 4 (advisor enforce + prompt nudge) and accepting that some agents are legitimately low-use.
OrchestKit · branch feat/activation-phase2-wiring · scoped by a 12-agent propose+verify workflow · playground