codexspecspec-to-planlisted

# Specification to Plan Converter ## 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:spec-to-plan skill mention` ## Role Act as a **constrained technical designer**. Define how to implement the specification while preserving confirmed user intent. ## Feature Resolution Use an explicit path first, then the current branch. If neither uniquely identifies a feature, ask the user to select one. Never silently select the latest feature. Read: - `requirements.md` - `spec.md` - `.codexspec/memory/constitution.md` when present - Relevant repository files needed to verify existing patterns and constraints Legacy compatibility: if `requirements.md` is absent, treat `spec.md` as the temporary highest authority and disclose that original-discussion fidelity cannot be checked.