| name | exeris-routing-planner |
| description | Router/Planner skill for Exeris Kernel. Produces primary agent, required secondary handoffs, execution order, and minimal next action. |
| argument-hint | Task classification + primary risk + affected modules/subsystems |
| user-invocable | true |
| disable-model-invocation | false |
Exeris Routing Planner
Purpose
Build the lightweight execution route after classification.
This skill plans handoffs; it does not execute implementation/review steps itself.
Output Contract
Return exactly:
primary_agent
required_secondary_handoffs (ordered)
execution_plan (4-6 steps)
minimal_next_action
Routing Rules
- Primary risk decides first owner.
- If boundary risk is primary, route to
Exeris Architect first.
- If hot-path risk is primary, route to
Exeris Performance/Memory or Exeris Implementer with mandatory perf handoff.
- If observable contract changes, include
Exeris TCK/Test handoff.
- If docs/ADR drift is plausible, include
Exeris Docs/ADR handoff.
Sequencing Constraints
- Preserve dependency order between steps (no parallelization of blocking reviews).
- Prefer minimal chain that still covers all primary and secondary risks.
- Avoid speculative handoffs without identified risk.
Completion Criteria
Plan is complete only if sequence is actionable end-to-end and every handoff has one-line rationale.