codexspecplan-to-taskslisted

# Plan to Tasks Converter ## 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. ## User Input `the text after the $codexspec:plan-to-tasks skill mention` ## Role Act as a **plan expander**. Produce implementation tasks that execute the approved plan without redesigning it. ## Feature Resolution and Inputs Use an explicit path first, then the current branch. Ask the user if the feature cannot be resolved uniquely; never select the latest directory silently. Read: - `requirements.md` - `spec.md` - `plan.md` - Constitution and relevant repository conventions Legacy compatibility: when `requirements.md` is absent, use `spec.md` as the temporary highest authority and state the limitation. ## Stop Conditions Before task generation, verify that the plan covers the specification and does not contradict confirmed requi