config

CodexSpec Configuration Manager

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.

A fresh or reset config writes only output; interaction and document resolve to it via the fallback above, so an output-only config is fully functional (non-blocking). Set interaction or document individually only to make them differ from output. That is why the YAML examples below stay output-only.

Parameter Check

Check if $ARGUMENTS contains --view:

• If --view is present: View mode - display current configuration and exit
• If no arguments: Interactive mode - show configuration management menu

Configuration File Path

All configuration operations target: .codexspec/config.yml

Instructions

Step 1: Check Configuration File Existence

First, check if .codexspec/config.yml exists:

• If the file exists: Read its contents and proceed to Step 2 or Step 3 (based on mode)
• If the file does not exist: Proceed to Step 4 (Create new configuration)

Step 2: View Mode (--view flag)

If --view flag is provided:

1. If configuration exists, display it in a readable format:

## Current Configuration

```yaml
{file contents}

Configuration file: .codexspec/config.yml

2. If configuration does not exist, display:

```markdown
## Configuration Not Found

No configuration file found at `.codexspec/config.yml`.

To create a new configuration, run `/codexspec:config` without arguments.