# Workflow Router

> Routes ambiguous or multi-domain engineering requests to the smallest ordered skill set. Do not use for clear single-skill work or same-task follow-ups.

- Skill: `mesteriis/workflow-router` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add mesteriis/workflow-router`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mesteriis/workflow-router/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector CAUTION)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Mesteriis (https://skillmd.com/u/mesteriis)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/mesteriis/workflow-router

---


# Workflow Router

Use this router only when the request is genuinely ambiguous, spans multiple
engineering domains, or needs an ordered handoff between workflows. A directly
requested leaf skill takes precedence.

## Fast Path

- Clear single-domain request: choose the narrowest leaf skill directly and do
  not use this router.
- Same-task follow-up: reuse the active route. Do not reread an unchanged
  `SKILL.md` already available in the conversation.
- Changed domain, risk class, external system, or requested workflow: route only
  the changed portion.

## Workflow

1. Classify the request by concrete deliverable and mutation risk.
2. Select one primary skill and at most one supporting skill by default.
3. Add another skill only when it contributes a distinct required procedure or
   evidence type.
4. Read only selected skills whose instructions are not already available.
5. Order mixed work by dependency, usually evidence or design before mutation,
   then validation.
6. If the common routes below are insufficient, read
   `references/routes.md` for the exhaustive route table.

## Common Routes

- Bug or failure investigation: `debugging` plus the relevant ecosystem skill.
- Behavior implementation: relevant ecosystem skill; add `testing-tdd` when
  regression coverage or test-first work is required.
- Explicit review: `code-review`; use `security-router` or `ui-router` when that
  domain is central.
- Refactor without behavior change: `refactoring` plus the ecosystem skill.
- Performance investigation: `performance` plus the ecosystem skill.
- Migration, architecture, multi-agent, external pack, durable memory, or
  runtime-capability selection: use the matching specialist route in the
  reference table.

## Output

Do not emit a routing preamble for an obvious route. Briefly state the route only
when the choice is ambiguous, the request needs multiple stages, or a limitation
changes the result.

## Healthcheck

When asked to verify installed routing, run:

```bash
bash ~/.codex/skills/workflow-router/scripts/validate-routing.sh
```