nx/skills/orchestration/SKILL.md
Use when unsure which agent to use for a task, or when coordinating work across multiple agents in a pipeline
npx skillsauth add hellblazer/nexus orchestrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reference skill for agent routing and pipeline coordination. See reference.md for routing tables, pipeline templates, and the decision framework.
There is no orchestrator agent — the caller (main conversation or skill) dispatches agents directly using the routing tables.
| Request Type | Primary Agent | Pipeline | |-------------|---------------|----------| | Plan a feature | strategic-planner | -> nx_plan_audit -> architect-planner | | Implement code | developer | -> code-review-expert -> test-validator | | Debug issue | debugger | -> (if cross-cutting) deep-analyst | | Review code | code-review-expert | -> (if critical) substantive-critic | | Research topic | deep-research-synthesizer | -> store_put (direct) | | Analyze system | codebase-deep-analyzer | -> (if deep) deep-analyst |
For the full routing graph, decision framework, and standard pipelines, see reference.md.
development
Use when critiquing / auditing / reviewing a change set against decision history — tries the review plan library first (catalog lookup → decision-evolution traversal → extract → compare), falls through to /nx:query if nothing matches
documentation
Use when doing design / architecture / planning work that walks from prose (RDRs, docs, knowledge) into the modules implementing a concept
development
Use when surveying the plan library's runtime metrics to propose plans for promotion to a higher scope — advisory-only; dispatches the plan-promote-propose meta-seed (no lifecycle ops — those ship in RDR-079)
business
Use when inspecting plan runtime metrics or enumerating dimension-registry usage — dispatches plan_match with dimensions={verb:plan-inspect}; strategy:default reports per-plan metrics, strategy:dimensions reports registry usage counts