Skip to content

Zts0hg/codexspec

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

217 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

CodexSpec Logo

CodexSpec

English | ไธญๆ–‡ | ๆ—ฅๆœฌ่ชž | Espaรฑol | Portuguรชs | ํ•œ๊ตญ์–ด | Deutsch | Franรงais

PyPI version Python License: MIT

A Spec-Driven Development (SDD) toolkit for Claude Code

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.

๐Ÿ“– Documentation | ไธญๆ–‡ๆ–‡ๆกฃ | ๆ—ฅๆœฌ่ชžใƒ‰ใ‚ญใƒฅใƒกใƒณใƒˆ | ํ•œ๊ตญ์–ด ๋ฌธ์„œ | Documentaciรณn | Documentation | Dokumentation | Documentaรงรฃo


Table of Contents


Why Choose CodexSpec?

Why use CodexSpec on top of Claude Code? Here's the comparison:

Aspect Claude Code Only CodexSpec + Claude Code
Multi-language Support Default English interaction Configure team language for smoother collaboration and reviews
Traceability Hard to trace decisions after session ends All specs, plans, and tasks saved in .codexspec/specs/
Session Recovery Plan mode interruptions are hard to recover from Multi-command split + persisted docs = easy recovery
Team Governance No unified principles, inconsistent styles constitution.md enforces team standards and quality

What is Spec-Driven Development?

Spec-Driven Development (SDD) is a "specifications first, code later" methodology:

Traditional:  Idea โ†’ Code โ†’ Debug โ†’ Rewrite
SDD:          Idea โ†’ Spec โ†’ Plan โ†’ Tasks โ†’ Code

Why use 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
โœจ Key Features

Core Workflow

  • Constitution-Based Development - Establish project principles that guide all decisions
  • Two-Phase Specification - Interactive clarification (/specify) followed by document generation (/generate-spec)
  • Automatic Reviews - Every artifact includes built-in quality checks
  • TDD-Ready Tasks - Task breakdowns enforce test-first methodology

Human-AI Collaboration

  • Review Commands - Dedicated review commands for spec, plan, and tasks
  • Interactive Clarification - Q&A-based requirement refinement
  • Cross-Artifact Analysis - Detect inconsistencies before implementation

Developer Experience

  • Native Claude Code Integration - Slash commands work seamlessly
  • Multi-Language Support - 13+ languages via LLM dynamic translation
  • Cross-Platform - Bash and PowerShell scripts included
  • Extensible - Plugin architecture for custom commands

Design Philosophy: Human-AI Collaboration

CodexSpec is built on the belief that effective AI-assisted development requires active human participation at every stage.

Why Human Oversight Matters

Without Reviews With Reviews
AI makes wrong assumptions Humans catch misunderstandings early
Incomplete requirements propagate Gaps identified before implementation
Architecture drifts from intent Alignment verified at each stage
Tasks miss critical features Systematic coverage validation
Result: Rework, wasted effort Result: Get it right the first time

The CodexSpec Approach

CodexSpec structures development into reviewable checkpoints:

Idea โ†’ /specify โ†’ /generate-spec โ†’ /spec-to-plan โ†’ /plan-to-tasks โ†’ /implement
                         โ”‚                  โ”‚                โ”‚
                    Review spec        Review plan      Review tasks
                         โ”‚                  โ”‚                โ”‚
                      โœ… Human            โœ… Human          โœ… Human

Every artifact has a corresponding review command:

  • spec.md โ†’ /codexspec:review-spec
  • plan.md โ†’ /codexspec:review-plan
  • tasks.md โ†’ /codexspec:review-tasks
  • All artifacts โ†’ /codexspec:analyze

This systematic review process ensures:

  • Early error detection: Catch misunderstandings before code is written
  • Alignment verification: Confirm AI's interpretation matches your intent
  • Quality gates: Validate completeness, clarity, and feasibility at each stage
  • Reduced rework: Invest minutes in review to save hours of reimplementation

๐Ÿš€ 30-Second Quick Start

# 1. Install
uv tool install codexspec

# 2. Initialize project
#    Option A: Create new project
codexspec init my-project && cd my-project

#    Option B: Initialize in existing project
cd your-existing-project && codexspec init .

# 3. Use in Claude Code
claude
> /codexspec:constitution Create principles focused on code quality and testing
> /codexspec:specify I want to build a todo application
> /codexspec:generate-spec
> /codexspec:spec-to-plan
> /codexspec:plan-to-tasks
> /codexspec:implement-tasks

That's it! Read on for the complete workflow.


Installation

Prerequisites

  • Python 3.11+
  • uv (recommended) or pip

Recommended Installation

# Using uv (recommended)
uv tool install codexspec

# Or using pip
pip install codexspec

Verify Installation

codexspec --version
๐Ÿ“ฆ Alternative Installation Methods

One-time Usage (No Installation)

# Create new project
uvx codexspec init my-project

# Initialize in existing project
cd your-existing-project
uvx codexspec init . --ai claude

Install Development Version from GitHub

# Using uv
uv tool install git+https://github.com/Zts0hg/codexspec.git

# Specify branch or tag
uv tool install git+https://github.com/Zts0hg/codexspec.git@main
uv tool install git+https://github.com/Zts0hg/codexspec.git@v0.5.6
๐ŸชŸ Notes for Windows Users

Recommended: Use PowerShell

# 1. Install uv (if not already installed)
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

# 2. Restart PowerShell, then install codexspec
uv tool install codexspec

# 3. Verify installation
codexspec --version

CMD Troubleshooting

If you encounter "Access denied" errors:

  1. Close all CMD windows and reopen
  2. Or manually refresh PATH: set PATH=%PATH%;%USERPROFILE%\.local\bin
  3. Or use full path: %USERPROFILE%\.local\bin\codexspec.exe --version

For detailed troubleshooting, see Windows Troubleshooting Guide.

Upgrade

# Using uv
uv tool install codexspec --upgrade

# Using pip
pip install --upgrade codexspec

Plugin Marketplace Installation (Alternative)

CodexSpec is also available as a Claude Code plugin. This method is ideal if you want to use CodexSpec commands directly in Claude Code without the CLI tool.

Installation Steps

# In Claude Code, add the marketplace
> /plugin marketplace add Zts0hg/codexspec

# Install the plugin
> /plugin install codexspec@codexspec-market

Language Configuration for Plugin Users

After installing via Plugin Marketplace, configure your preferred language using the /codexspec:config command:

# Start interactive configuration
> /codexspec:config

# Or view current configuration
> /codexspec:config --view

The config command will guide you through:

  1. Selecting output language (for generated documents)
  2. Selecting commit message language
  3. Creating the .codexspec/config.yml file

Comparison of Installation Methods

Method Best For Features
CLI Installation (uv tool install) Full development workflow CLI commands (init, check, config) + slash commands
Plugin Marketplace Quick start, existing projects Slash commands only (use /codexspec:config for language setup)

Note: The plugin uses strict: false mode and reuses the existing multi-language support via LLM dynamic translation.


Core Workflow

CodexSpec breaks development into reviewable checkpoints:

Idea โ†’ /specify โ†’ /generate-spec โ†’ /spec-to-plan โ†’ /plan-to-tasks โ†’ /implement
                         โ”‚                  โ”‚                โ”‚
                    Review spec        Review plan      Review tasks
                         โ”‚                  โ”‚                โ”‚
                      โœ… Human            โœ… Human          โœ… Human

Workflow Steps

Step Command Output Human Check
1. Project Principles /codexspec:constitution constitution.md โœ…
2. Requirement Clarification /codexspec:specify None (interactive dialogue) โœ…
3. Generate Spec /codexspec:generate-spec spec.md + auto-review โœ…
4. Technical Planning /codexspec:spec-to-plan plan.md + auto-review โœ…
5. Task Breakdown /codexspec:plan-to-tasks tasks.md + auto-review โœ…
6. Cross-Artifact Analysis /codexspec:analyze Analysis report โœ…
7. Implementation /codexspec:implement-tasks Code -

specify vs clarify: When to Use Which?

Aspect /codexspec:specify /codexspec:clarify
Purpose Initial requirement exploration Refine existing spec
When to Use No spec.md exists yet spec.md needs improvement
Output None (dialogue only) Updates spec.md
Method Open-ended Q&A Structured scan (4 categories)
Questions Unlimited Max 5 per run

Key Concept: Iterative Quality Loop

Every generation command includes automatic review, generating a review report. You can:

  1. Review the report
  2. Describe issues to fix in natural language
  3. System automatically updates specs and review reports
%%{init: {
  'theme': 'base',
  'themeVariables': {
    'lineColor': '#888888',
    'primaryColor': '#2d2d2d',
    'primaryTextColor': '#ffffff',
    'primaryBorderColor': '#666666'
  },
  'flowchart': {
    'curve': 'stepBefore',
    'nodeSpacing': 50,
    'rankSpacing': 40
  }
}}%%
flowchart TB
    classDef rectStyle fill:#2d2d2d,stroke:#666,stroke-width:1px,color:#fff,width:220px;
    classDef diamondStyle fill:#3d3d3d,stroke:#888,stroke-width:2px,color:#fff;

    A["Generate Spec/Plan/Tasks"]:::rectStyle --> B["Auto Review"]:::rectStyle
    B --> C{"Issues Found?"}:::diamondStyle

    C -->|Yes| D["Describe Fix in Natural Language"]:::rectStyle
    D --> E["Update Spec + Review Report"]:::rectStyle

    E --> B

    C -->|No| F["Continue to Next Step"]:::rectStyle

    linkStyle 2,4 stroke:#aaa,stroke-width:1px;
Loading
๐Ÿ“– Detailed Workflow Description

1. Initialize Project

codexspec init my-awesome-project
cd my-awesome-project
claude

2. Establish Project Principles

/codexspec:constitution Create principles focused on code quality, testing standards, and clean architecture

3. Clarify Requirements

/codexspec:specify I want to build a task management application

This command will:

  • Ask clarifying questions to understand your idea
  • Explore edge cases you might not have considered
  • NOT generate files automatically - you stay in control

4. Generate Specification Document

Once requirements are clarified:

/codexspec:generate-spec

This command:

  • Compiles clarified requirements into structured specification
  • Automatically runs review and generates review-spec.md

5. Create Technical Plan

/codexspec:spec-to-plan Use Python FastAPI for backend, PostgreSQL for database, React for frontend

Includes constitutionality review - verifies plan aligns with project principles.

6. Generate Tasks

/codexspec:plan-to-tasks

Tasks are organized into standard phases:

  • TDD Enforcement: Test tasks precede implementation tasks
  • Parallel Markers [P]: Identify independent tasks
  • File Path Specifications: Clear deliverables per task

7. Cross-Artifact Analysis (Optional but Recommended)

/codexspec:analyze

Detects issues across spec, plan, and tasks:

  • Coverage gaps (requirements without tasks)
  • Duplication and inconsistencies
  • Constitution violations
  • Underspecified items

8. Implementation

/codexspec:implement-tasks

Implementation follows conditional TDD workflow:

  • Code tasks: Test-first (Red โ†’ Green โ†’ Verify โ†’ Refactor)
  • Non-testable tasks (docs, config): Direct implementation

Available Commands

CLI Commands

Command Description
codexspec init Initialize a new project
codexspec check Check for installed tools
codexspec version Display version information
codexspec config View or modify configuration
๐Ÿ“‹ init Options
Option Description
PROJECT_NAME Project directory name
--here, -h Initialize in current directory
--ai, -a AI assistant to use (default: claude)
--lang, -l Output language (e.g., en, zh-CN, ja)
--force, -f Force overwrite existing files
--no-git Skip git initialization
--debug, -d Enable debug output
๐Ÿ“‹ config Options
Option Description
--set-lang, -l Set output language
--set-commit-lang, -c Set commit message language
--list-langs List all supported languages

Slash Commands

Core Workflow Commands

Command Description
/codexspec:constitution Create/update project constitution with cross-artifact validation
/codexspec:specify Clarify requirements through interactive Q&A
/codexspec:generate-spec Generate spec.md document โ˜… Auto-review
/codexspec:spec-to-plan Convert spec to technical plan โ˜… Auto-review
/codexspec:plan-to-tasks Break down plan into atomic tasks โ˜… Auto-review
/codexspec:implement-tasks Execute tasks (conditional TDD)

Review Commands (Quality Gates)

Command Description
/codexspec:review-spec Review specification (auto or manual)
/codexspec:review-plan Review technical plan (auto or manual)
/codexspec:review-tasks Review task breakdown (auto or manual)

Enhancement Commands

Command Description
/codexspec:config Manage project configuration (create/view/modify/reset)
/codexspec:clarify Scan spec for ambiguities (4 categories, max 5 questions)
/codexspec:analyze Cross-artifact consistency analysis (read-only, severity-based)
/codexspec:checklist Generate requirements quality checklist
/codexspec:tasks-to-issues Convert tasks to GitHub Issues

Git Workflow Commands

Command Description
/codexspec:commit-staged Generate commit message from staged changes
/codexspec:pr Generate PR/MR description (auto-detect platform)

Code Review Commands

Command Description
/codexspec:review-code Review code in any language (idiomatic clarity, correctness, robustness, architecture)

Comparison with spec-kit

CodexSpec is inspired by GitHub spec-kit with key differences:

Feature spec-kit CodexSpec
Core Philosophy Spec-driven development Spec-driven + Human-AI collaboration
CLI Name specify codexspec
Primary AI Multi-agent support Focused on Claude Code
Constitution System Basic Full constitution + cross-artifact validation
Two-Phase Spec No Yes (clarify + generate)
Review Commands Optional 3 dedicated review commands + scoring
Clarify Command Yes 4 focus categories, review integration
Analyze Command Yes Read-only, severity-based, constitution-aware
TDD in Tasks Optional Enforced (tests before implementation)
Implementation Standard Conditional TDD (code vs docs/config)
Extension System Yes Yes
PowerShell Scripts Yes Yes
i18n Support No Yes (13+ languages via LLM translation)

Key Differentiators

  1. Review-First Culture: Every major artifact has a dedicated review command
  2. Constitution Governance: Principles are validated, not just documented
  3. TDD by Default: Test-first methodology enforced in task generation
  4. Human Checkpoints: Workflow designed around validation gates

Internationalization (i18n)

CodexSpec supports multiple languages through LLM dynamic translation. No translation templates to maintain - Claude translates content at runtime based on your language configuration.

Setting Language

During initialization:

# Create Chinese output project
codexspec init my-project --lang zh-CN

# Create Japanese output project
codexspec init my-project --lang ja

After initialization:

# View current configuration
codexspec config

# Change output language
codexspec config --set-lang zh-CN

# Set commit message language
codexspec config --set-commit-lang en

Supported Languages

Code Language
en English (default)
zh-CN ็ฎ€ไฝ“ไธญๆ–‡
zh-TW ็น้ซ”ไธญๆ–‡
ja ๆ—ฅๆœฌ่ชž
ko ํ•œ๊ตญ์–ด
es Espaรฑol
fr Franรงais
de Deutsch
pt-BR Portuguรชs
ru ะ ัƒััะบะธะน
it Italiano
ar ุงู„ุนุฑุจูŠุฉ
hi เคนเคฟเคจเฅเคฆเฅ€
โš™๏ธ Configuration File Example

.codexspec/config.yml:

version: "1.0"

language:
  output: "zh-CN"        # Output language
  commit: "zh-CN"        # Commit message language (defaults to output)
  templates: "en"        # Keep as "en"

project:
  ai: "claude"
  created: "2025-02-15"

Project Structure

Project structure after initialization:

my-project/
โ”œโ”€โ”€ .codexspec/
โ”‚   โ”œโ”€โ”€ memory/
โ”‚   โ”‚   โ””โ”€โ”€ constitution.md    # Project constitution
โ”‚   โ”œโ”€โ”€ specs/
โ”‚   โ”‚   โ””โ”€โ”€ {feature-id}/
โ”‚   โ”‚       โ”œโ”€โ”€ spec.md        # Feature specification
โ”‚   โ”‚       โ”œโ”€โ”€ plan.md        # Technical plan
โ”‚   โ”‚       โ”œโ”€โ”€ tasks.md       # Task breakdown
โ”‚   โ”‚       โ””โ”€โ”€ checklists/    # Quality checklists
โ”‚   โ”œโ”€โ”€ templates/             # Custom templates
โ”‚   โ”œโ”€โ”€ scripts/               # Helper scripts
โ”‚   โ””โ”€โ”€ extensions/            # Custom extensions
โ”œโ”€โ”€ .claude/
โ”‚   โ””โ”€โ”€ commands/              # Claude Code slash commands
โ””โ”€โ”€ CLAUDE.md                  # Claude Code context

Extension System

CodexSpec supports a plugin architecture for custom commands:

my-extension/
โ”œโ”€โ”€ extension.yml          # Extension manifest
โ”œโ”€โ”€ commands/              # Custom slash commands
โ”‚   โ””โ”€โ”€ command.md
โ””โ”€โ”€ README.md

See extensions/EXTENSION-DEVELOPMENT-GUIDE.md for details.


Development

Prerequisites

  • Python 3.11+
  • uv package manager
  • Git

Local Development

# Clone repository
git clone https://github.com/Zts0hg/codexspec.git
cd codexspec

# Install dev dependencies
uv sync --dev

# Run locally
uv run codexspec --help

# Run tests
uv run pytest

# Lint code
uv run ruff check src/

# Build package
uv build

Contributing

Contributions are welcome! Please read the contributing guidelines before submitting a pull request.

License

MIT License - see LICENSE for details.

Acknowledgements