codexspecgenerate-speclisted

# Specification Generator ## 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:generate-spec skill mention` ## Role Act as a **requirements compiler**. Convert the persistent, user-confirmed decision record into `spec.md` without changing product intent. ## Authority Order 1. Confirmed entries in `requirements.md` 2. Existing `spec.md` when operating in legacy compatibility mode 3. Project constitution and verified repository facts 4. Explicit assumptions, which are never equivalent to confirmed requirements 5. General best practices ## Feature Resolution 1. If `the text after the $codexspec:generate-spec skill mention` identifies a `requirements.md` file or feature directory, use it. 2. Otherwise match the current git branch to `.codexspec/specs/<branch>/`. 3. If the