From nx
Use when unsure which agent to use for a task, or when coordinating work across multiple agents in a pipeline
npx claudepluginhub hellblazer/nexus --plugin nxThis skill uses the workspace's default tool permissions.
Delegates to the **orchestrator** agent (sonnet). See [registry.yaml](../../registry.yaml).
Orchestrates subagents by delegating tasks to role-matched specialists like engineer, reviewer, analyst for multi-agent coding workflows.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Share bugs, ideas, or general feedback.
Delegates to the orchestrator agent (sonnet). See registry.yaml.
digraph routing {
rankdir=TB;
"Request type?" [shape=diamond];
"Plan a feature" [shape=box];
"Implement code" [shape=box];
"Debug issue" [shape=box];
"Review code" [shape=box];
"Research topic" [shape=box];
"Analyze system" [shape=box];
"strategic-planner" [shape=ellipse];
"plan-auditor" [shape=ellipse];
"architect-planner" [shape=ellipse];
"developer" [shape=ellipse];
"code-review-expert" [shape=ellipse];
"test-validator" [shape=ellipse];
"debugger" [shape=ellipse];
"deep-analyst" [shape=ellipse];
"substantive-critic" [shape=ellipse];
"deep-research-synthesizer" [shape=ellipse];
"knowledge-tidier" [shape=ellipse];
"codebase-deep-analyzer" [shape=ellipse];
"Request type?" -> "Plan a feature" [label="plan/design"];
"Request type?" -> "Implement code" [label="build/implement"];
"Request type?" -> "Debug issue" [label="test failure/bug"];
"Request type?" -> "Review code" [label="review/quality"];
"Request type?" -> "Research topic" [label="research/investigate"];
"Request type?" -> "Analyze system" [label="explore/understand"];
"Plan a feature" -> "strategic-planner";
"strategic-planner" -> "plan-auditor" [label="then"];
"plan-auditor" -> "architect-planner" [label="then"];
"Implement code" -> "developer";
"developer" -> "code-review-expert" [label="then"];
"developer" -> "debugger" [label="on escalation"];
"debugger" -> "developer" [label="fix applied, resume"];
"code-review-expert" -> "test-validator" [label="then"];
"Debug issue" -> "debugger";
"debugger" -> "deep-analyst" [label="if cross-cutting"];
"Review code" -> "code-review-expert";
"code-review-expert" -> "substantive-critic" [label="if critical"];
"Research topic" -> "deep-research-synthesizer";
"deep-research-synthesizer" -> "knowledge-tidier" [label="then"];
"Analyze system" -> "codebase-deep-analyzer";
"codebase-deep-analyzer" -> "deep-analyst" [label="if deep"];
}
Use the Agent tool to invoke orchestrator:
## Relay: orchestrator
**Task**: [what needs to be done]
**Bead**: [ID] or 'none'
### Input Artifacts
- Files: [relevant files]
### Deliverable
Routing decision with recommended agent
### Quality Criteria
- [ ] User goal clearly understood
- [ ] Appropriate agent(s) identified
- [ ] Clear rationale provided
For full relay structure and optional fields, see RELAY_TEMPLATE.md.
| Request Type | Primary Agent | Pipeline |
|---|---|---|
| Plan a feature | strategic-planner | -> plan-auditor -> architect-planner |
| Implement code | developer | -> code-review-expert -> test-validator |
| Implement code (circuit breaker fired) | debugger | [after developer stops] -> debugger -> developer resumes |
| Debug issue | debugger | -> (if cross-cutting) deep-analyst |
| Review code | code-review-expert | -> (if critical) substantive-critic |
| Research topic | deep-research-synthesizer | -> knowledge-tidier |
| Analyze system | codebase-deep-analyzer | -> (if deep) deep-analyst |