From devflow
Classify a coding task into tiny/standard/deep/debug and route each phase to a Fable agent with a pinned effort level. Canonical routing rules + effort matrix for devflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devflow:devflow-adaptive-routingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pick exactly one mode, then assign model tiers. This file is the ONLY source of the routing rules and the model matrix — commands reference it, never restate it.
Pick exactly one mode, then assign model tiers. This file is the ONLY source of the routing rules and the model matrix — commands reference it, never restate it.
Conflicts: debug + deep → start debug (root cause first), escalate to deep after root cause. Unsure tiny vs standard → standard. Unsure standard vs deep → deep. Unfamiliar code → never tiny.
| Task | Default |
|---|---|
| SQL extraction / cleanup / formatting | tiny (standard if restructuring the query) |
| New endpoint / service / repo method | standard |
| Bug, failing test, 500, crash, container exit | debug |
| Review only (no implementation) | /devflow-review |
| Deployment / config troubleshooting (Docker, env, secrets) | debug |
| Architecture / data model / migration / payments / auth refactor | deep |
One model everywhere: Fable (model: fable). Tiers differ by effort, not model. Both are pinned in each agent's frontmatter (agents/*.md) — the Agent tool has no per-call effort param, and a per-call model= would override frontmatter. Commands therefore never pass model= on dispatch; picking the agent picks the tier.
| Tier | Effort | Agents | Use for |
|---|---|---|---|
| max-reasoning | xhigh | devflow-planner | planning, specs |
| working | medium | devflow-plan-reviewer, devflow-implementer, devflow-reviewer, devflow-debugger, devflow-scout | plan review, implementation, review, verification, debugging, discovery |
Inline work (tiny mode, orchestration) runs at the session model + session effort. Update this table and the agent frontmatter together when models or effort levels change.
| Mode | Phase | Agent (effort) |
|---|---|---|
| tiny | all (inline — no subagent) | session model @ session effort |
| standard | discovery + design (one dispatch) | devflow-planner (xhigh) |
| standard | plan review | devflow-plan-reviewer (medium) |
| standard | implementation | devflow-implementer (medium) |
| standard | review + verify | devflow-reviewer (medium) |
| deep | discovery (standalone pass) | devflow-scout (medium) |
| deep | spec + plan | devflow-planner (xhigh) |
| deep | plan review | devflow-plan-reviewer (medium) |
| deep | implementation | devflow-implementer (medium) |
| deep | review + verify | devflow-reviewer (medium) |
| debug | all | devflow-debugger (medium) |
Planning always runs max-reasoning — never downgrade it. A wrong plan executed perfectly is wasted work. Everything else — plan review, implementation, review, debugging, discovery — runs medium: reasoning budget is reserved for producing the plan, and a good plan makes medium-effort execution sufficient.
Escalation: tiny-mode ESCALATE → re-classify as standard.
Immediately before every Agent dispatch, print one line in the conversation (hooks cannot render this; only your own text is guaranteed visible):
▸ devflow-planner · fable @ xhigh
Agent → effort: planner = xhigh, plan-reviewer/implementer/reviewer/debugger/scout = medium. Same values as the agents' frontmatter — frontmatter is the source of truth.
Mode: <mode> — <one sentence naming the deciding rule>
Route: <phase>=<agent>, ...
Two lines. No filler. No alternatives listed.
npx claudepluginhub latsode/devflow --plugin devflowGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.