codexspecclarifylisted

# Requirements Clarifier ## 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:clarify skill mention` ## Feature Resolution Use an explicit path first, then the current branch. Ask the user when resolution is ambiguous; never silently select the latest feature. Read: - `requirements.md` - `spec.md` - `review-spec.md` when present - Constitution Legacy compatibility: when only `spec.md` exists, extract candidate requirement records with `Status: open`. Do not assume the extracted wording reflects the original discussion until the user confirms it. ## Clarification Priorities Prioritize: 1. Confirmed requirement and spec mismatches 2. Critical or Warning defects from `review-spec.md` 3. Open items that block planning 4. Material ambiguity, contradiction, missing behavi