codexspecimplement-taskslisted

# Task Implementer ## Language Preference Read `.codexspec/config.yml`. Two independent language controls apply (each falls back to `language.output`, then English): - **Interaction language** (`language.interaction`): language for all conversation with the user — questions, explanations, status messages, and `codexspec` CLI terminal output. - **Document language** (`language.document`): language for generated artifact files (requirements/spec/plan/tasks). Converse in the interaction language and author artifacts in the document language. Apply the project's translation standard to both: translate by meaning (not word-for-word), keep English for terms with no good native equivalent, and write as if originally in that language. ## Feature Resolution Resolve the feature in this order: 1. Use an explicit path from `the text after the $codexspec:implement-tasks skill mention` when it identifies a `tasks.md` file or feature directory. 2. Otherwise match the current branch, which must use the timestamp format, to `.codexspec/specs/<branch>/`. 3. If no unique feature can be resolved, ask the user to select one. Never silently select the latest workspace. Derive all artifact paths from the selected feature directory. All implementation-side output belongs to that workspace. ## Input Documents and Authority Read: - `requirements.md` - `spec.md` - `plan.md` - `tasks.md` - `.codexspec/memory/constitution.md` when present Authority order: 1. Confirmed entries in `re