codexspecchecklistlisted

# Requirements Quality Checklist Generator ## Constitution Compliance (MANDATORY) **Before generating checklists:** 1. **Check for Constitution File**: Look for `.codexspec/memory/constitution.md` 2. **If Constitution Exists**: - Load and read quality standards and project principles - Use constitution quality standards as baseline for checklist items - Include constitution-specific checklist items where relevant 3. **If No Constitution Exists**: Use general best practices for requirements quality ## 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. ## Checklist Purpose: "Unit Tests for Requirements" **CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements. **NOT for verification/testing:** - ❌ NOT "Verify the butt