Menü
Use first for normal or high-risk natural-language work to choose task mode, tier, grill path, spec layers, team-rule scan, and required gates before implementation.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | intent-routing |
| description | Use first for normal or high-risk natural-language work to choose task mode, tier, grill path, spec layers, team-rule scan, and required gates before implementation. |
Use this skill before meaningful edits when the user gives a natural-language request.
trivial, normal, or high-risk.grill-me, grill-with-docs, domain language, L1/L2/L3 spec, UI/runtime evidence, strict review, or team-rule mining.docs/ai/current/Intent-Routing.json.scripts/harness/intent_router_gate.py.Return the route, required gates, and why the route was selected. Do not silently skip the routing artifact for normal+ work.
Explicit GPT-5.6 native-first router for auditing, designing, installing, or validating Codex skill combinations, global skill setup, routing fixtures, and harness behavior. Use when the user explicitly invokes $codex-skill-router or asks to change or inspect Codex skills, routing, AGENTS guidance, or global harness configuration. Do not use for ordinary coding, review, debugging, research, or UI work merely because the task is complex.
Use when work introduces or changes shared nouns, states, IDs, ownership, authority, or customer-facing vocabulary.
Use when changing harness gates, routing rules, skills, or automation behavior and benchmark/eval evidence is needed to avoid slowing normal coding performance. Do not use for ordinary app code changes.
Use when a request is early, ambiguous, or lacks a codebase-backed shared language; interview the user to expose assumptions before planning.
Use when a codebase, docs, ADRs, tests, prior reviews, or team traces exist; align new work with existing shared language before implementation.
Use before claiming normal+ completion when accepted REQ statements must be mapped to executed tests, guardrails, smoke checks, runtime/UI evidence, or named manual review.