codexspecanalyzelisted

# Cross-Artifact Analyzer ## 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:analyze skill mention` ## Operating Constraints This command is read-only. Do not modify artifacts. Resolve the feature by explicit path, then current branch. Ask the user if it is ambiguous; never select the latest feature silently. ## Inputs Load: - `requirements.md` - `spec.md` - `plan.md` - `tasks.md` - Constitution Legacy compatibility: if `requirements.md` is missing, state that the analysis starts at `spec.md` and cannot validate fidelity to the original discussion. ## End-to-End Traceability Build the chain: ```text confirmed NEED/CON/DEC/OUT -> REQ/NFR Sources -> plan Covers -> task Covers + Plan reference ``` Detect: - Confirmed requirements with no spec coverage - Spe