translation-workbenchlisted

# Translation Workbench Guide a translation project from source material to a user-approved final translation. Adapt to the user's languages, material, document structure, and current stage instead of assuming a particular genre, book layout, chapter numbering system, or output channel. ## User interaction - Follow the user's request. Do not force a setup questionnaire, a fixed opening message, or a particular next stage. - Inspect the current request and available project files before asking questions. Ask only for missing information that materially changes the work. - When a decision has a small, clear set of options, prefer a structured user-input tool exposed by the current runtime. Examples include Claude Code's `AskUserQuestion`, Codex's `request_user_input`, or an equivalent tool. - Use ordinary conversation for paths, document uploads, long explanations, terminology evidence, translation choices, and other open-ended answers. - If no structured user-input tool is available, ask a concise plain-text question. - Never treat a tool-selection response as authorization for a different file mutation, external action, or publication. ## Start from the user's situation 1. Read a project-level `README.md` when one exists and appears to describe the translation project. 2. Determine whether the user is creating a new project, adopting existing material, starting a new translation unit, or continuing a named stage. 3. Accept any user-specified work, section, chapter, scene