codexspec 0.6.0__tar.gz → 0.6.2__tar.gz

{codexspec-0.6.0 → codexspec-0.6.2}/.gitignore

@@ -7,15 +7,10 @@
 /local-ref/
 
 # Project specific
-# .codexspec/ holds per-project SDD state (specs, plans, tasks, scripts, config).
-# Keep it ignored to avoid leaking the maintainer's zh-CN working artifacts into
-# this English-facing open-source repo. Exception: constitution.md is governance
-# and must be tracked so the "SUPREME AUTHORITY" claim is real for contributors.
-.codexspec/*
-!.codexspec/.gitkeep
-!.codexspec/memory/
-.codexspec/memory/*
-!.codexspec/memory/constitution.md
+# .codexspec/ holds per-project SDD state (specs, plans, tasks, scripts, config,
+# memory). The entire directory is tracked in version control so the project's
+# full SDD history is public and reproducible. Add per-file ignores below only
+# if a specific artifact must stay local (none currently).
 
 # Promotion content archive (local drafts, not meant for the repo)
 promotion-posts.md

{codexspec-0.6.0 → codexspec-0.6.2}/PKG-INFO

@@ -1,14 +1,14 @@
 Metadata-Version: 2.4
 Name: codexspec
-Version: 0.6.0
-Summary: CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code
+Version: 0.6.2
+Summary: CodexSpec - A Requirements-First SDD toolkit for Claude Code
 Project-URL: Homepage, https://github.com/Zts0hg/codexspec
 Project-URL: Repository, https://github.com/Zts0hg/codexspec
 Project-URL: Issues, https://github.com/Zts0hg/codexspec/issues
 Author: CodexSpec Team
 License: MIT
 License-File: LICENSE
-Keywords: ai,claude,cli,sdd,spec-driven-development
+Keywords: ai,claude,cli,requirements-driven,requirements-first,sdd,spec-driven-development
 Classifier: Development Status :: 3 - Alpha
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
@@ -51,18 +51,24 @@ Description-Content-Type: text/markdown
   </picture>
 </div>
 
-# CodexSpec
+<h1 align="center">CodexSpec</h1>
 
-**English** | [中文](README.zh-CN.md) | [日本語](README.ja.md) | [Español](README.es.md) | [Português](README.pt-BR.md) | [한국어](README.ko.md) | [Deutsch](README.de.md) | [Français](README.fr.md)
+<p align="center">
+  <b>English</b> | <a href="README.zh-CN.md">中文</a> | <a href="README.ja.md">日本語</a> | <a href="README.es.md">Español</a> | <a href="README.pt-BR.md">Português</a> | <a href="README.ko.md">한국어</a> | <a href="README.de.md">Deutsch</a> | <a href="README.fr.md">Français</a>
+</p>
 
-[![PyPI version](https://img.shields.io/pypi/v/codexspec.svg)](https://pypi.org/project/codexspec/)
-[![Python](https://img.shields.io/pypi/pyversions/codexspec.svg)](https://pypi.org/project/codexspec/)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+<p align="center">
+  <a href="https://pypi.org/project/codexspec/"><img src="https://img.shields.io/pypi/v/codexspec.svg?style=for-the-badge" alt="PyPI version"></a>
+  <a href="https://pypi.org/project/codexspec/"><img src="https://img.shields.io/pypi/pyversions/codexspec.svg?style=for-the-badge" alt="Python versions"></a>
+  <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-yellow?style=for-the-badge" alt="License: MIT"></a>
+</p>
 
-**A Spec-Driven Development (SDD) toolkit for Claude Code**
+<p align="center">
+  <strong>A Requirements-First SDD toolkit for Claude Code</strong>
+</p>
 
-CodexSpec helps you build high-quality software through a structured, specification-first approach.
-Instead of jumping straight to code, you define **what** to build and **why** before deciding **how** to build it.
+CodexSpec helps you build high-quality software through **Requirements-First Spec-Driven Development (SDD)** — confirmed requirements come first, and nothing is binding until you explicitly confirm it.
+Instead of jumping straight to code, you confirm **what** to build and **why** before deciding **how** to build it.
 
 [📖 Documentation](https://zts0hg.github.io/codexspec/) | [中文文档](https://zts0hg.github.io/codexspec/zh/) | [日本語ドキュメント](https://zts0hg.github.io/codexspec/ja/) | [한국어 문서](https://zts0hg.github.io/codexspec/ko/) | [Documentación](https://zts0hg.github.io/codexspec/es/) | [Documentation](https://zts0hg.github.io/codexspec/fr/) | [Dokumentation](https://zts0hg.github.io/codexspec/de/) | [Documentação](https://zts0hg.github.io/codexspec/pt-BR/)
 
@@ -71,7 +77,7 @@ Instead of jumping straight to code, you define **what** to build and **why** be
 ## Table of Contents
 
 - [Why Choose CodexSpec?](#why-choose-codexspec)
-- [What is Spec-Driven Development?](#what-is-spec-driven-development)
+- [What is Requirements-First SDD?](#what-is-requirements-first-sdd)
 - [Design Philosophy: Human-AI Collaboration](#design-philosophy-human-ai-collaboration)
 - [30-Second Quick Start](#-30-second-quick-start)
 - [Installation](#installation)
@@ -96,23 +102,23 @@ Why use CodexSpec on top of Claude Code? Here's the comparison:
 
 ---
 
-## What is Spec-Driven Development?
+## What is Requirements-First SDD?
 
-**Spec-Driven Development (SDD)** is a "specifications first, code later" methodology:
+**Requirements-First SDD** is the Spec-Driven Development (SDD) methodology with one upgrade: **confirmed requirements are the highest-priority authority**. You define and confirm *what* to build and *why* before deciding *how* — and nothing becomes binding until you explicitly confirm it.
 
 ```
 Traditional:  Idea → Code → Debug → Rewrite
 SDD:          Idea → Confirmed Requirements → Spec → Plan → Tasks → Code
 ```
 
-**Why use SDD?**
+**Why use Requirements-First SDD?**
 
-| Problem              | SDD Solution                                     |
-| -------------------- | ------------------------------------------------ |
-| AI misunderstandings | Specs clarify "what to build", AI stops guessing |
-| Missing requirements | Interactive clarification discovers edge cases   |
-| Architecture drift   | Review checkpoints ensure correct direction      |
-| Wasted rework        | Problems are found before code is written        |
+| Problem              | Requirements-First SDD Solution                          |
+| -------------------- | -------------------------------------------------------- |
+| AI misunderstandings | Confirmed requirements tell AI "what to build"; AI stops guessing |
+| Missing requirements | Interactive clarification + a confirmation gate surface edge cases |
+| Architecture drift   | Review checkpoints ensure correct direction              |
+| Wasted rework        | Problems are found and confirmed before code is written  |
 
 <details>
 <summary>✨ Key Features</summary>
@@ -595,7 +601,7 @@ CodexSpec is inspired by GitHub spec-kit with key differences:
 
 | Feature             | spec-kit                | CodexSpec                                     |
 | ------------------- | ----------------------- | --------------------------------------------- |
-| Core Philosophy     | Spec-driven development | Spec-driven + Human-AI collaboration          |
+| Core Philosophy     | Spec-driven development | Requirements-First SDD + Human-AI collaboration |
 | CLI Name            | `specify`               | `codexspec`                                   |
 | Primary AI          | Multi-agent support     | Focused on Claude Code                        |
 | Constitution System | Basic                   | Full constitution + cross-artifact validation |
@@ -614,7 +620,7 @@ CodexSpec is inspired by GitHub spec-kit with key differences:
 1. **Review-First Culture**: Every major artifact has a dedicated review command
 2. **Constitution Governance**: Principles are validated, not just documented
 3. **Evidence-Based Review**: Defects require concrete evidence; advisory design ideas do not affect acceptance
-4. **Human Checkpoints**: Workflow designed around validation gates
+4. **Confirmation Gate**: Requirements, specs, plans, and tasks become binding only after explicit human confirmation
 
 ---
 

{codexspec-0.6.0 → codexspec-0.6.2}/README.md

@@ -6,18 +6,24 @@
   </picture>
 </div>
 
-# CodexSpec
+<h1 align="center">CodexSpec</h1>
 
-**English** | [中文](README.zh-CN.md) | [日本語](README.ja.md) | [Español](README.es.md) | [Português](README.pt-BR.md) | [한국어](README.ko.md) | [Deutsch](README.de.md) | [Français](README.fr.md)
+<p align="center">
+  <b>English</b> | <a href="README.zh-CN.md">中文</a> | <a href="README.ja.md">日本語</a> | <a href="README.es.md">Español</a> | <a href="README.pt-BR.md">Português</a> | <a href="README.ko.md">한국어</a> | <a href="README.de.md">Deutsch</a> | <a href="README.fr.md">Français</a>
+</p>
 
-[![PyPI version](https://img.shields.io/pypi/v/codexspec.svg)](https://pypi.org/project/codexspec/)
-[![Python](https://img.shields.io/pypi/pyversions/codexspec.svg)](https://pypi.org/project/codexspec/)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+<p align="center">
+  <a href="https://pypi.org/project/codexspec/"><img src="https://img.shields.io/pypi/v/codexspec.svg?style=for-the-badge" alt="PyPI version"></a>
+  <a href="https://pypi.org/project/codexspec/"><img src="https://img.shields.io/pypi/pyversions/codexspec.svg?style=for-the-badge" alt="Python versions"></a>
+  <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-yellow?style=for-the-badge" alt="License: MIT"></a>
+</p>
 
-**A Spec-Driven Development (SDD) toolkit for Claude Code**
+<p align="center">
+  <strong>A Requirements-First SDD toolkit for Claude Code</strong>
+</p>
 
-CodexSpec helps you build high-quality software through a structured, specification-first approach.
-Instead of jumping straight to code, you define **what** to build and **why** before deciding **how** to build it.
+CodexSpec helps you build high-quality software through **Requirements-First Spec-Driven Development (SDD)** — confirmed requirements come first, and nothing is binding until you explicitly confirm it.
+Instead of jumping straight to code, you confirm **what** to build and **why** before deciding **how** to build it.
 
 [📖 Documentation](https://zts0hg.github.io/codexspec/) | [中文文档](https://zts0hg.github.io/codexspec/zh/) | [日本語ドキュメント](https://zts0hg.github.io/codexspec/ja/) | [한국어 문서](https://zts0hg.github.io/codexspec/ko/) | [Documentación](https://zts0hg.github.io/codexspec/es/) | [Documentation](https://zts0hg.github.io/codexspec/fr/) | [Dokumentation](https://zts0hg.github.io/codexspec/de/) | [Documentação](https://zts0hg.github.io/codexspec/pt-BR/)
 
@@ -26,7 +32,7 @@ Instead of jumping straight to code, you define **what** to build and **why** be
 ## Table of Contents
 
 - [Why Choose CodexSpec?](#why-choose-codexspec)
-- [What is Spec-Driven Development?](#what-is-spec-driven-development)
+- [What is Requirements-First SDD?](#what-is-requirements-first-sdd)
 - [Design Philosophy: Human-AI Collaboration](#design-philosophy-human-ai-collaboration)
 - [30-Second Quick Start](#-30-second-quick-start)
 - [Installation](#installation)
@@ -51,23 +57,23 @@ Why use CodexSpec on top of Claude Code? Here's the comparison:
 
 ---
 
-## What is Spec-Driven Development?
+## What is Requirements-First SDD?
 
-**Spec-Driven Development (SDD)** is a "specifications first, code later" methodology:
+**Requirements-First SDD** is the Spec-Driven Development (SDD) methodology with one upgrade: **confirmed requirements are the highest-priority authority**. You define and confirm *what* to build and *why* before deciding *how* — and nothing becomes binding until you explicitly confirm it.
 
 ```
 Traditional:  Idea → Code → Debug → Rewrite
 SDD:          Idea → Confirmed Requirements → Spec → Plan → Tasks → Code
 ```
 
-**Why use SDD?**
+**Why use Requirements-First SDD?**
 
-| Problem              | SDD Solution                                     |
-| -------------------- | ------------------------------------------------ |
-| AI misunderstandings | Specs clarify "what to build", AI stops guessing |
-| Missing requirements | Interactive clarification discovers edge cases   |
-| Architecture drift   | Review checkpoints ensure correct direction      |
-| Wasted rework        | Problems are found before code is written        |
+| Problem              | Requirements-First SDD Solution                          |
+| -------------------- | -------------------------------------------------------- |
+| AI misunderstandings | Confirmed requirements tell AI "what to build"; AI stops guessing |
+| Missing requirements | Interactive clarification + a confirmation gate surface edge cases |
+| Architecture drift   | Review checkpoints ensure correct direction              |
+| Wasted rework        | Problems are found and confirmed before code is written  |
 
 <details>
 <summary>✨ Key Features</summary>
@@ -550,7 +556,7 @@ CodexSpec is inspired by GitHub spec-kit with key differences:
 
 | Feature             | spec-kit                | CodexSpec                                     |
 | ------------------- | ----------------------- | --------------------------------------------- |
-| Core Philosophy     | Spec-driven development | Spec-driven + Human-AI collaboration          |
+| Core Philosophy     | Spec-driven development | Requirements-First SDD + Human-AI collaboration |
 | CLI Name            | `specify`               | `codexspec`                                   |
 | Primary AI          | Multi-agent support     | Focused on Claude Code                        |
 | Constitution System | Basic                   | Full constitution + cross-artifact validation |
@@ -569,7 +575,7 @@ CodexSpec is inspired by GitHub spec-kit with key differences:
 1. **Review-First Culture**: Every major artifact has a dedicated review command
 2. **Constitution Governance**: Principles are validated, not just documented
 3. **Evidence-Based Review**: Defects require concrete evidence; advisory design ideas do not affect acceptance
-4. **Human Checkpoints**: Workflow designed around validation gates
+4. **Confirmation Gate**: Requirements, specs, plans, and tasks become binding only after explicit human confirmation
 
 ---
 

codexspec-0.6.2/codexspec-logo-dark.svg

@@ -0,0 +1,36 @@
+<svg viewBox="0 0 420 96" xmlns="http://www.w3.org/2000/svg">
+  <defs>
+    <style>
+      .mono {
+        font-family: 'JetBrains Mono','Fira Code','SF Mono','Consolas','Courier New',monospace;
+      }
+    </style>
+  </defs>
+
+  <!-- Background -->
+  <rect width="420" height="96" rx="12" fill="#0d1117"/>
+
+  <!-- ── Wordmark: {code} × <spec> ── -->
+
+  <!-- { -->
+  <text class="mono" x="51"  y="47" font-size="40" font-weight="700" fill="#58a6ff" dominant-baseline="middle">{</text>
+  <!-- code -->
+  <text class="mono" x="77"  y="47" font-size="33" font-weight="500" fill="#e6edf3" dominant-baseline="middle">code</text>
+  <!-- } -->
+  <text class="mono" x="160" y="47" font-size="40" font-weight="700" fill="#58a6ff" dominant-baseline="middle">}</text>
+
+  <!-- × operator -->
+  <text class="mono" x="210" y="46" font-size="26" font-weight="700" fill="#f0883e" dominant-baseline="middle" text-anchor="middle">×</text>
+
+  <!-- < -->
+  <text class="mono" x="236" y="47" font-size="40" font-weight="700" fill="#3fb950" dominant-baseline="middle">&lt;</text>
+  <!-- spec -->
+  <text class="mono" x="262" y="47" font-size="33" font-weight="500" fill="#e6edf3" dominant-baseline="middle">spec</text>
+  <!-- > -->
+  <text class="mono" x="345" y="47" font-size="40" font-weight="700" fill="#3fb950" dominant-baseline="middle">&gt;</text>
+
+  <!-- Tagline: three words centered under the wordmark columns {code} × <spec> -->
+  <text class="mono" x="118.5" y="75" font-size="9" font-weight="400" fill="#6e7681" text-anchor="middle" letter-spacing="2.8">SPEC</text>
+  <text class="mono" x="211.0" y="75" font-size="9" font-weight="400" fill="#6e7681" text-anchor="middle" letter-spacing="2.8">DRIVEN</text>
+  <text class="mono" x="304.0" y="75" font-size="9" font-weight="400" fill="#6e7681" text-anchor="middle" letter-spacing="2.8">DEVELOPMENT</text>
+</svg>

codexspec-0.6.2/codexspec-logo-light.svg

@@ -0,0 +1,36 @@
+<svg viewBox="0 0 420 96" xmlns="http://www.w3.org/2000/svg">
+  <defs>
+    <style>
+      .mono {
+        font-family: 'JetBrains Mono','Fira Code','SF Mono','Consolas','Courier New',monospace;
+      }
+    </style>
+  </defs>
+
+  <!-- Background -->
+  <rect width="420" height="96" rx="12" fill="#ffffff" stroke="#d0d7de" stroke-width="1"/>
+
+  <!-- ── Wordmark: {code} × <spec> ── -->
+
+  <!-- { -->
+  <text class="mono" x="51"  y="47" font-size="40" font-weight="700" fill="#0969da" dominant-baseline="middle">{</text>
+  <!-- code -->
+  <text class="mono" x="77"  y="47" font-size="33" font-weight="500" fill="#1f2328" dominant-baseline="middle">code</text>
+  <!-- } -->
+  <text class="mono" x="160" y="47" font-size="40" font-weight="700" fill="#0969da" dominant-baseline="middle">}</text>
+
+  <!-- × operator -->
+  <text class="mono" x="210" y="46" font-size="26" font-weight="700" fill="#bc4c00" dominant-baseline="middle" text-anchor="middle">×</text>
+
+  <!-- < -->
+  <text class="mono" x="236" y="47" font-size="40" font-weight="700" fill="#1a7f37" dominant-baseline="middle">&lt;</text>
+  <!-- spec -->
+  <text class="mono" x="262" y="47" font-size="33" font-weight="500" fill="#1f2328" dominant-baseline="middle">spec</text>
+  <!-- > -->
+  <text class="mono" x="345" y="47" font-size="40" font-weight="700" fill="#1a7f37" dominant-baseline="middle">&gt;</text>
+
+  <!-- Tagline: three words centered under the wordmark columns {code} × <spec> -->
+  <text class="mono" x="118.5" y="75" font-size="9" font-weight="400" fill="#8c959f" text-anchor="middle" letter-spacing="2.8">SPEC</text>
+  <text class="mono" x="211.0" y="75" font-size="9" font-weight="400" fill="#8c959f" text-anchor="middle" letter-spacing="2.8">DRIVEN</text>
+  <text class="mono" x="304.0" y="75" font-size="9" font-weight="400" fill="#8c959f" text-anchor="middle" letter-spacing="2.8">DEVELOPMENT</text>
+</svg>

{codexspec-0.6.0 → codexspec-0.6.2}/pyproject.toml

@@ -1,14 +1,14 @@
 [project]
 name = "codexspec"
-version = "0.6.0"
-description = "CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code"
+version = "0.6.2"
+description = "CodexSpec - A Requirements-First SDD toolkit for Claude Code"
 readme = "README.md"
 requires-python = ">=3.11"
 license = { text = "MIT" }
 authors = [
     { name = "CodexSpec Team" }
 ]
-keywords = ["sdd", "spec-driven-development", "claude", "ai", "cli"]
+keywords = ["requirements-first", "sdd", "spec-driven-development", "requirements-driven", "claude", "ai", "cli"]
 classifiers = [
     "Development Status :: 3 - Alpha",
     "Environment :: Console",
@@ -64,13 +64,21 @@ build-backend = "hatchling.build"
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/codexspec"]
-force-include = { "templates" = "codexspec/templates", "scripts" = "codexspec/scripts" }
+# scripts/ is split by AUDIENCE:
+#   - bash/ + powershell/ -> user-facing, copied verbatim by `codexspec init`
+#   - python/             -> maintainer-only tooling (auto-responder, notifier...)
+# force-include does NOT honor .gitignore, so we ship ONLY the two user subdirs;
+# including all of scripts/ would leak scripts/python/.env (secrets), notify
+# logs, and maintainer-only scripts. Other maintainer tools live in /internal
+# (outside scripts/ entirely). The sdist `include` below mirrors this boundary.
+force-include = { "templates" = "codexspec/templates", "scripts/bash" = "codexspec/scripts/bash", "scripts/powershell" = "codexspec/scripts/powershell" }
 
 [tool.hatch.build.targets.sdist]
 include = [
     "/src",
     "/templates",
-    "/scripts",
+    "/scripts/bash",
+    "/scripts/powershell",
     "/codexspec-icon.svg",
     "/codexspec-logo-dark.svg",
     "/codexspec-logo-light.svg",

{codexspec-0.6.0 → codexspec-0.6.2}/src/codexspec/__init__.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code.
+CodexSpec - A Requirements-First SDD toolkit for Claude Code.
 
 This toolkit provides a structured approach to software development using
 executable specifications that guide AI-assisted implementation.
@@ -30,12 +30,13 @@ from .commands.installer import (
 from .i18n import (
     generate_config_content,
     get_commit_language,
+    get_interaction_language,
     get_language_name,
-    get_project_language,
     get_supported_languages,
     is_supported_language,
     normalize_locale,
     update_config_language,
+    update_language_field,
     update_output_language,
 )
 from .translator import translate
@@ -51,7 +52,7 @@ MARKDOWNLINT_DISABLE_MD041 = "<!-- markdownlint-disable MD041 -->\n"
 
 app = typer.Typer(
     name="codexspec",
-    help="CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code",
+    help="CodexSpec - A Requirements-First SDD toolkit for Claude Code",
     add_completion=False,
 )
 console = Console()
@@ -185,6 +186,16 @@ def config(
         "-c",
         help="Set the commit message language (defaults to output language)",
     ),
+    set_interaction_lang: Optional[str] = typer.Option(
+        None,
+        "--set-interaction-lang",
+        help="Set the interaction language (LLM dialogue + codexspec CLI terminal output)",
+    ),
+    set_document_lang: Optional[str] = typer.Option(
+        None,
+        "--set-document-lang",
+        help="Set the document language (generated requirements/spec/plan/tasks files)",
+    ),
     list_langs: bool = typer.Option(
         False,
         "--list-langs",
@@ -322,6 +333,45 @@ def config(
         console.print(f"[green]Commit message language set to:[/green] {normalized} ({lang_name})")
         return
 
+    # Handle set interaction language
+    if set_interaction_lang:
+        normalized = normalize_locale(set_interaction_lang)
+        if not is_supported_language(normalized):
+            console.print(
+                f"[yellow]Warning: '{set_interaction_lang}' is not in the list of "
+                "commonly supported languages.[/yellow]"
+            )
+            console.print(
+                "It may still work if Claude supports it. "
+                "Run [cyan]codexspec config --list-langs[/cyan] to see supported languages."
+            )
+        if update_language_field(config_file, "interaction", normalized):
+            lang_name = get_language_name(normalized)
+            console.print(f"[green]Interaction language set to:[/green] {normalized} ({lang_name})")
+        else:
+            console.print("[red]Failed to update interaction language setting[/red]")
+            raise typer.Exit(1)
+        return
+
+    # Handle set document language
+    if set_document_lang:
+        normalized = normalize_locale(set_document_lang)
+        if not is_supported_language(normalized):
+            console.print(
+                f"[yellow]Warning: '{set_document_lang}' is not in the list of commonly supported languages.[/yellow]"
+            )
+            console.print(
+                "It may still work if Claude supports it. "
+                "Run [cyan]codexspec config --list-langs[/cyan] to see supported languages."
+            )
+        if update_language_field(config_file, "document", normalized):
+            lang_name = get_language_name(normalized)
+            console.print(f"[green]Document language set to:[/green] {normalized} ({lang_name})")
+        else:
+            console.print("[red]Failed to update document language setting[/red]")
+            raise typer.Exit(1)
+        return
+
     # Display current configuration
     console.print(
         Panel(
@@ -340,8 +390,8 @@ def list_commands() -> None:
     showing their display names and descriptions.
     """
 
-    # Get user's language preference
-    language = get_project_language()
+    # Get user's language preference (CLI terminal output uses the interaction language)
+    language = get_interaction_language()
 
     metadata = get_installed_commands_metadata()
 
@@ -935,8 +985,9 @@ This document provides comprehensive context and guidelines for Claude Code when
 
 ## Project Overview
 
-This project uses the **CodexSpec** methodology - a Spec-Driven Development (SDD) approach
-that emphasizes specifications as executable artifacts that directly guide implementation.
+This project uses the **CodexSpec** methodology - a Requirements-First Spec-Driven Development (SDD)
+approach where confirmed requirements are the highest-priority authority, and nothing is binding
+until explicitly confirmed. Specifications and plans are executable artifacts that guide implementation.
 
 ## Available Commands
 

{codexspec-0.6.0 → codexspec-0.6.2}/src/codexspec/commands/installer.py

@@ -57,49 +57,49 @@ def get_commands_metadata() -> list[CommandMetadata]:
         {
             "name": "specify",
             "display_name": "/codexspec:specify",
-            "description": "通过交互式问答明确需求，探索'做什么'和'为什么'",
+            "description": "讨论、确认并固化权威的需求记录",
             "category": "core",
             "file_name": "specify.md",
         },
         {
             "name": "generate-spec",
             "display_name": "/codexspec:generate-spec",
-            "description": "从已明确的需求生成详细的 spec.md 规格文档",
+            "description": "将已确认的需求编写为可追溯的 spec.md",
             "category": "core",
             "file_name": "generate-spec.md",
         },
         {
             "name": "spec-to-plan",
             "display_name": "/codexspec:spec-to-plan",
-            "description": "将功能规格转换为技术实现计划",
+            "description": "将已确认的规格转换为可追溯的技术计划",
             "category": "core",
             "file_name": "spec-to-plan.md",
         },
         {
             "name": "plan-to-tasks",
             "display_name": "/codexspec:plan-to-tasks",
-            "description": "将技术计划分解为可执行的任务列表",
+            "description": "将已批准的计划展开为可追溯、可执行的任务",
             "category": "core",
             "file_name": "plan-to-tasks.md",
         },
         {
             "name": "review-spec",
             "display_name": "/codexspec:review-spec",
-            "description": "审查功能规格的完整性和质量",
+            "description": "审查规格的忠实度、内部质量与计划就绪度",
             "category": "core",
             "file_name": "review-spec.md",
         },
         {
             "name": "review-plan",
             "display_name": "/codexspec:review-plan",
-            "description": "审查技术计划的可行性和对齐度",
+            "description": "审查计划的忠实度、可行性与实现就绪度",
             "category": "core",
             "file_name": "review-plan.md",
         },
         {
             "name": "review-tasks",
             "display_name": "/codexspec:review-tasks",
-            "description": "审查任务分解的完整性和 TDD 合规性",
+            "description": "审查任务的忠实度、可执行性、依赖关系与验证",
             "category": "core",
             "file_name": "review-tasks.md",
         },
@@ -114,14 +114,14 @@ def get_commands_metadata() -> list[CommandMetadata]:
         {
             "name": "clarify",
             "display_name": "/codexspec:clarify",
-            "description": "在技术规划前提出澄清问题",
+            "description": "解决需求歧义，并将 requirements.md 与 spec.md 同步",
             "category": "enhanced",
             "file_name": "clarify.md",
         },
         {
             "name": "analyze",
             "display_name": "/codexspec:analyze",
-            "description": "跨工件一致性和质量分析",
+            "description": "分析 SDD 工件间的端到端可追溯性与一致性",
             "category": "enhanced",
             "file_name": "analyze.md",
         },
@@ -173,7 +173,7 @@ def get_commands_metadata() -> list[CommandMetadata]:
         {
             "name": "quick",
             "display_name": "/codexspec:quick",
-            "description": "小需求的一站式快速实现 — 自动完成 spec、plan、tasks 和代码",
+            "description": "为小型变更运行精简的 Requirements-First SDD 流程",
             "category": "utility",
             "file_name": "quick.md",
         },