codexspecquicklisted

# Quick Implementation ## 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:quick skill mention` ## Scope Check Quick is intended for a small, well-bounded change. Assess likely files, module span, new dependencies, and unresolved product decisions. If the change is broad or has multiple independent outcomes, explain why the standard flow is safer and ask whether to continue with Quick. ## Compact Requirement Confirmation Even in Quick mode, do not rely on session-only context. 1. Resolve only ambiguities that materially change implementation. 2. Create a feature workspace and `requirements.md` using the same timestamp feature convention as `$codexspec:specify`. 3. Present a concise confirmed requirement summary containing: - `NEED-*` - relevant `CON-*` and `DEC