Subagents
Delegate to focused child agents — scout, reviewer, planner, worker, oracle, and run them in parallel.
@elyracode/subagents lets Elyra split a task across narrow, single‑purpose agents. Each subagent has its own role, tool access, and prompt, so it produces sharper results than asking one generalist to do everything.
Install
elyra install npm:@elyracode/subagents
Agents
| Agent | Use when you want… |
|---|---|
scout |
Fast codebase recon — files, structure, data flow, risks |
reviewer |
Code review — correctness, tests, edge cases, security, simplicity |
planner |
Implementation plan with concrete steps and file paths |
worker |
Implementation — edits files, validates, follows the plan |
oracle |
Second opinion — challenges assumptions, catches drift |
researcher |
External research — docs, specs, recent changes |
delegate |
General‑purpose child agent for ad‑hoc tasks |
Read‑only agents (scout, reviewer, planner, oracle, researcher) cannot edit files. Worker is the only agent permitted to write.
Commands
| Command | Description |
|---|---|
/run <agent> <task> |
Run a single subagent |
/parallel <a> '..' -> <b> '..' |
Run multiple subagents in parallel |
/build-feature |
scout → planner → oracle → worker → reviewer → worker (fix) |
/ui-review |
worker (build) → reviewer (screenshot + visual QA) → worker (fix) → reviewer (verify) |
/deep-review |
reviewer (correctness) → reviewer (tests) → reviewer (security) → oracle (synthesis) |
/git-review |
Review the current git diff for correctness, security, tests, debt |
/setup-git-hook |
Install a pre-push hook that runs /git-review automatically |
/agents |
Show available subagents |
Examples
Use reviewer to review this diff.
Ask oracle for a second opinion on my plan.
Use scout to understand the auth flow.
Run parallel reviewers: one for correctness, one for tests, one for complexity.
Have worker implement this plan, then run reviewer to check it.
/run scout analyze the authentication flow
/run reviewer review the changes in the last commit
/parallel reviewer 'check correctness' -> reviewer 'check tests' -> reviewer 'check complexity'
/build-feature add a wallet system with balance tracking
/deep-review the authentication system
Git integration
/git-review produces a go/no‑go verdict on staged and unstaged changes. Combine it with /setup-git-hook to block pushes that fail review (skip with git push --no-verify).
Recommended workflow
scout → planner → worker → reviewer → worker (fixes)
Each step is focused. Scout maps the problem, planner writes the path, worker executes, reviewer hardens — and oracle is your final sanity check.