Workflow Skill Router
Make your Claude Code and Codex workflow repeatable.
One lead Skill per phase, only the support that phase needs, and your workflow saved as config you can reuse.
繁體中文 · Documentation · Install · See a route · Evidence and limits
Workflow Skill Router is an open-source Plugin for Claude Code and Codex. Before your agent starts work, it picks the Skill that should lead the current phase, adds only the support that phase needs, and shows you the plan. You define the workflow once, and the Router applies it to every task.
What you get
- A focused route for each phase. Planning an API change does not pull in implementation or deployment Skills before they are needed.
- Your choices stay in charge. When you name a Skill, it leads. Support outside your choice needs your consent first.
- Your workflow as config. A personal or workspace Skill Tree maps tasks to Skills and completion checks. The same Profile works in Claude Code and Codex.
- A clear record of what ran. A Skill in the plan is not treated as a Skill the environment can use. When the work ends, you see planned and actual Skill usage side by side.
Install
Both Plugins need Node.js 24+ and Python 3.11+. They include the compiled MCP bundle and Python runtime, so you do not need npm.
Claude Code
Claude Code support starts with v2.1.0.
/plugin marketplace add eric861129/Workflow-skill-router
/plugin install workflow-skill-router@workflow-skill-router
Claude Code reads the workspace Profile from .claude/workflow-skill-router.json first and falls back to .codex/workflow-skill-router.json. Personal Profiles and local state are shared with the Codex Plugin. See the Claude Code installation guide.
Codex Plugin + MCP
The published release is v2.1.2. Use this pinned release for a normal Codex installation. It fixes plan_work for requests that name a Skill without the skill: prefix; v2.1.0 added the Claude Code Plugin and opt-in Workflow Memory; Memory keeps persistent local plans and consent records alongside the routing instructions.
codex plugin marketplace add eric861129/Workflow-skill-router --ref v2.1.2
codex plugin add workflow-skill-router@workflow-skill-router
codex plugin list
Development main may contain later work that is not in v2.1.2. The Plugin installation guide explains how to verify the result.
Standalone Skill
Choose this mode for routing instructions without the local MCP runtime. Download the v2.1.2 Skill package and extract its inner workflow-skill-router/ folder into your Codex Skills directory.
The Skill-only installation guide covers the paths and setup. This mode guides model behavior; it cannot persist or enforce the Plugin's consent state machine. No installation includes every specialist Skill your workflow may reference.
Check that it works
In a new Claude Code session or a new Codex task, ask: “Show the Workflow Skill Router status and explain which capabilities are available in this environment.” The answer should report the bundled-local-r0 runtime and list what is available here.
See a route
The bundled workspace Profile example defines an API delivery workflow. With that Profile in place, a request in the api domain such as “Deliver the api contract, implementation, and tests” produces a phased plan like this:
| Phase | Primary Skill | Support in that phase | Exit gate |
|---|
| contract | api-designer | api-guidelines-skill | contract-reviewed |
| implementation | csharp-developer | none | implementation-complete |
| verification | qa-test-planner | playwright | tests-passed |
Only the current phase's Skills become the active route. The next phase is routed again when it starts. Every planned Skill stays intended-unverified until the runtime confirms it is installed and available. This shows configurable behavior, not a measured development outcome.
When it helps
| Your situation | What the Router adds |
|---|
| You have overlapping Skills and keep explaining which one should lead | A reusable personal or workspace routing profile |
| Your work moves through planning, implementation, and verification | A separate Skill selection and completion check for each phase |
| You need to resume work with dependencies across projects | A local work graph with explicit next steps; native Goal integration requires host support |
| You have one small task and a clear Skill choice | A small route; additional configuration may add little value |
This is the beginning of the README. Read the rest at the original. Read the full README ↗
