Run any Skill in Manus with one click

routing-policy-change

Stars2

Forks0

UpdatedMarch 26, 2026 at 12:24

Modifies routing policy after signal extraction, including matched-decision logic, candidate-model selection, and downstream looper behavior. Use when changing decision predicates, thresholds, priorities, model ranking, cost or latency routing, or other post-signal routing policy.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

BruceLoveDecimal

BruceLoveDecimal/semantic-router

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

More from this repository

same repository

claude-code-install

BruceLoveDecimal/semantic-router

Guides coding agents through a session-isolated install of the vllm-sr CLI. The install is scoped to a temporary directory so it does not modify the user's global PATH or system packages. Use when an agent or user wants to try vllm-sr without a permanent install.

2026-04-212

routing-calibration-loop

BruceLoveDecimal/semantic-router

Calibrates routing changes against a live router endpoint with executable probes, local DSL validation, versioned deploys, and structured failure review. Use when tuning signals, projections, decisions, or maintained route examples against a real apiserver.

2026-04-022

maintainer-issue-pr-management

BruceLoveDecimal/semantic-router

Manages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.

2026-04-022

architecture-guardrails

BruceLoveDecimal/semantic-router

Runs an explicit structural review for boundary-sensitive edits that need dependency, module, and structure-rule scrutiny without forcing that material into every default context pack. Use when a task crosses hotspot boundaries, adds new seams, or needs a deliberate architecture pass.

2026-03-262

config-platform-change

BruceLoveDecimal/semantic-router

Synchronizes config representations across router config, Python CLI schema, and dashboard config UI. Use when adding or changing a config concept that spans those surfaces or addressing config representation debt before Kubernetes-facing translation.

2026-03-262

dashboard-platform-runtime

BruceLoveDecimal/semantic-router

Maintains dashboard frontend and backend implementation slices that present, configure, or expose router behavior through the console. Use when the task changes dashboard config flows, console backend handlers, topology rendering, playground reveal flows, or other user-visible routing metadata in the dashboard.

2026-03-262

name	routing-policy-change
category	primary
description	Modifies routing policy after signal extraction, including matched-decision logic, candidate-model selection, and downstream looper behavior. Use when changing decision predicates, thresholds, priorities, model ranking, cost or latency routing, or other post-signal routing policy.

Routing Policy Change

Trigger

Change boolean decision logic after signal extraction
Change candidate-model selection, ranking, cost routing, or latency routing
Change looper behavior that belongs to matched-decision policy instead of signal extraction or plugin hooks

Workflow

Read change surfaces, module boundaries, and the Go router playbook for routing-policy context
Modify decision predicates, downstream model selection, or matched-decision looper behavior
Run make agent-report ENV=cpu CHANGED_FILES="..." to identify impacted surfaces
Run make agent-ci-gate CHANGED_FILES="..." to validate all affected constraints
Verify routing-policy behavior is covered by targeted tests and affected E2E expectations

Gotchas

Keep signal extraction upstream; do not smuggle classifier changes into this primary unless the signal contract itself is changing.
Keep plugin hooks separate; looper changes that only support matched-decision policy belong here, but request or response body plugins still belong to the plugin flow.
Decision predicates and candidate-model ranking can change user-visible routing even when the patch looks small, so they are not refactors by default.

Must Read

Standard Commands

make agent-report ENV=cpu CHANGED_FILES="..."
make agent-ci-gate CHANGED_FILES="..."
make agent-feature-gate ENV=cpu CHANGED_FILES="..."

Acceptance

Decision predicates and downstream candidate-model selection stay aligned with the same routing-policy intent
Targeted tests and affected E2E coverage are updated when routing-policy behavior changes
Routing-policy logic stays downstream of signal extraction and separate from plugin-only processing