Agents
The plugin has 5 agents split into two categories based on what tools they need.
Spawnable agents (read-only)
Section titled “Spawnable agents (read-only)”These use only Glob, Grep, LS, Read — safe to spawn via the Task tool, typically in parallel.
| Agent | Model | Purpose |
|---|---|---|
rn-code-explorer | Sonnet | Codebase mapping: screens, store, navigation, testIDs |
rn-code-architect | Opus | Architecture design with E2E proof flow |
rn-code-reviewer | Sonnet | Correctness, RN conventions, project patterns |
Parent-session-only agents (protocol playbooks)
Section titled “Parent-session-only agents (protocol playbooks)”These agents’ protocols require cdp_* / device_* MCP tools. Do NOT spawn them via the Task tool — MCP stdio connections don’t propagate across subprocess boundaries (see GitHub #31). The agent files are protocol playbooks the parent session reads and executes inline.
| Agent | Model | Purpose | How to invoke |
|---|---|---|---|
rn-tester | Sonnet | 7-step test verification protocol | /rn-dev-agent:test-feature — runs inline |
rn-debugger | Opus | Parallel evidence gathering + targeted fix | /rn-dev-agent:debug-screen — runs inline |
When agents are used
Section titled “When agents are used”In the rn-feature-dev pipeline:
- Phase 2 (Exploration): 2-3
rn-code-exploreragents spawned in parallel - Phase 4 (Architecture):
rn-code-architectspawned for blueprint design - Phase 5.5 (Verification): Verification runs inline in parent session (MCP tools)
- Phase 6 (Review): 2-3
rn-code-revieweragents spawned in parallel - Phase 8 (E2E Proof): Proof flow runs inline in parent session (MCP tools)
Standalone:
/rn-dev-agent:debug-screen— runs thern-debuggerprotocol inline/rn-dev-agent:test-feature— runs thern-testerprotocol inline