using-translation-toolkit

Entry router for the translation-toolkit plugin. Inspect the user's request — intent + the shape of the input they handed in — and route to one of the 5 active specialist skills (translation-i18n, translation-doc, translation-creative, translation-novel, translation-audit), preceded by translation-intake if the brief is ambiguous. This router does not translate, audit, or rewrite anything itself — it only decides which downstream skill should run.

When to use

• User asks for a translation between en-US / ja-JP / zh-TW / zh-CN and has not named a specific specialist skill.
• User provides translatable content (i18n file / markdown doc / ad copy / existing translation pair) but no explicit pipeline.
• Triggers (any locale): "translate / 翻訳して / 翻譯一下 / 翻译", "i18n / localize / 本地化 / ローカライズ", "audit translation / 翻訳レビュー / 翻譯審核", "transcreation / トランスクリエーション".

When NOT to use

• User explicitly names a downstream skill ("run translation-i18n on this PO file") — call it directly.
• Task is outside translation scope: copywriting → copywriting-toolkit, original-language drafting → domain-teams:copywriting-team, technical-doc authoring (not translating) → domain-teams:docs-team.
• Locale pair is outside the v0.1.0 supported set (en-US ↔ ja-JP ↔ zh-TW ↔ zh-CN). For other languages, tell the user the toolkit cannot guarantee glossary coverage and ask if they want to proceed with degraded quality.

Routing rules

Pick exactly one downstream specialist. If multiple signals fire, the input-shape rule wins over the intent rule (an explicit PO file always routes to i18n even if the user says "creative").