codexspecreview-speclisted

# Specification Reviewer ## 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:review-spec skill mention` ## Review Authority Resolve the feature by explicit path, then current branch. Never silently select the latest feature. Read `requirements.md`, `spec.md`, and the constitution. If `requirements.md` is absent, enter legacy compatibility mode: use `spec.md` as temporary authority and state that fidelity to the original discussion cannot be verified. Authority order: 1. Confirmed requirements and decisions 2. The specification being reviewed 3. Constitution and verified repository facts 4. Applicable best practices ## Review Passes ### 1. Fidelity - Map every confirmed `NEED`, `CON`, `DEC`, and `OUT` entry to the specification. - Detect omissions, semantic changes,