codexspecconstitutionlisted

## 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 ```text the text after the $codexspec:constitution skill mention ``` ## Input Mode Detection Parse `the text after the $codexspec:constitution skill mention` to determine execution mode: **Mode A: No Arguments** → Present exploration options and let user choose **Mode B: Exploration Keyword (`quick` or `deep`)** → Execute the corresponding exploration mode **Mode C: Project Principles Description** → Use provided principles directly, skip exploration --- ### Mode A: No Arguments - Present Options **IMPORTANT**: Use the `AskUserQuestion` tool to present structured choices. ```json { "questions": [{ "question": "I will explore the project to generate the constitution. Please select exploration depth:", "header": "Exploration", "opti