codexspecspecifylisted

# Requirement Discovery ## 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:specify skill mention` ## Goal Turn the user discussion into a persistent, traceable `requirements.md`. The discussion is the richest source of intent, but only the user's confirmed stage summary becomes binding downstream authority. Do not generate `spec.md` in this command. ## Feature Workspace ### New Feature When `the text after the $codexspec:specify skill mention` is a new requirement: 1. Derive a short kebab-case feature name. 2. Run the platform create-new-feature script: - Bash: `.codexspec/scripts/create-new-feature.sh --name "<feature-name>"` - PowerShell: `.codexspec/scripts/create-new-feature.ps1 -ShortName "<feature-name>" "<description>"` 3. Parse the created feature dir