Version npm License Stars Issues

**[English](README.md) | [δΈ­ζ–‡](README_CN.md)**
Typing SVG

Quick Start Guide CLI Tools Architecture

--- ## ✨ Key Features
### 🎯 4-Level Workflows From `lite-lite-lite` (instant) to `brainstorm` (multi-role analysis) ### πŸ”„ Multi-CLI Orchestration Gemini, Qwen, Codex, Claude - auto-select or manual ### ⚑ Dependency-Aware Parallelism Agent parallel execution without worktree complexity ### πŸ”§ Issue Workflow Post-development maintenance with optional worktree isolation ### πŸ“¦ JSON-First State `.task/IMPL-*.json` as single source of truth ### πŸ–₯️ Dashboard Visual session management, CodexLens search, graph explorer
> πŸ“– **New?** See [Workflow Guide](WORKFLOW_GUIDE.md) for the complete 4-level workflow system. --- ## πŸš€ Quick Start ### Install CCW ```bash npm install -g claude-code-workflow ccw install -m Global ``` ### Choose Your Workflow Level
LevelCommandUse Case
1/workflow:lite-lite-liteQuick fixes, config changes
2/workflow:lite-planClear single-module features
2/workflow:lite-fixBug diagnosis and fix
2/workflow:multi-cli-planMulti-perspective analysis
3/workflow:planMulti-module development
3/workflow:tdd-planTest-driven development
4/workflow:brainstorm:auto-parallelNew features, architecture design
### Workflow Examples ```bash # Level 1: Instant execution /workflow:lite-lite-lite "Fix typo in README" # Level 2: Lightweight planning /workflow:lite-plan "Add JWT authentication" /workflow:lite-fix "User upload fails with 413 error" # Level 3: Standard planning with session /workflow:plan "Implement payment gateway integration" /workflow:execute # Level 4: Multi-role brainstorming /workflow:brainstorm:auto-parallel "Design real-time collaboration system" --count 5 /workflow:plan --session WFS-xxx /workflow:execute ``` --- ## πŸ› οΈ CLI Tool Installation
CLIDescriptionOfficial Docs
GeminiGoogle AI analysisgoogle-gemini/gemini-cli
CodexOpenAI autonomous codingopenai/codex
OpenCodeOpen-source multi-modelopencode-ai/opencode
QwenAlibaba Qwen-CodeQwenLM/Qwen
--- ## 🎭 Semantic CLI Invocation

Users can **semantically specify CLI tools** in prompts - the system automatically invokes the corresponding CLI. ### Basic Invocation
| User Prompt | System Action | |-------------|---------------| | "Use Gemini to analyze the auth module" | Auto-invoke `gemini` CLI for analysis | | "Let Codex review this code" | Auto-invoke `codex` CLI for review | | "Ask Qwen about performance optimization" | Auto-invoke `qwen` CLI for consultation |
### Multi-CLI Orchestration
| Pattern | User Prompt Example | |---------|---------------------| | **Collaborative** | "Use Gemini and Codex to collaboratively analyze security vulnerabilities" | | **Parallel** | "Have Gemini, Codex, and Qwen analyze the architecture in parallel" | | **Iterative** | "Use Gemini to diagnose, then Codex to fix, iterate until resolved" | | **Pipeline** | "Gemini designs the solution, Codex implements, Claude reviews" |
πŸ“ More Examples ```text # Single CLI invocation User: "Use Gemini to analyze the database query performance" β†’ System auto-calls: gemini CLI with analysis task # Collaborative analysis User: "Use Gemini and Codex to collaboratively review the authentication flow" β†’ System auto-calls: gemini + codex CLIs, synthesizes results # Parallel multi-perspective User: "Have all available CLIs analyze this architecture design in parallel" β†’ System auto-calls: gemini, codex, qwen in parallel β†’ merged report # Sequential pipeline User: "Use Gemini to plan the refactoring, then Codex to implement it" β†’ System auto-calls: gemini (plan) β†’ codex (implement) sequentially ```
### Custom CLI Registration Register **any API as a custom CLI** via Dashboard interface: ```bash ccw view # Open Dashboard β†’ Status β†’ API Settings β†’ Add Custom CLI ```
| Field | Example | |-------|---------| | **Name** | `deepseek` | | **Endpoint** | `https://api.deepseek.com/v1/chat` | | **API Key** | `your-api-key` |
> βš™οΈ Register once, invoke semantically forever - no code changes needed. --- ## πŸ” ACE Tool Configuration ACE (Augment Context Engine) provides powerful semantic code search.
| Method | Link | |--------|------| | **Official** | [Augment MCP Documentation](https://docs.augmentcode.com/context-services/mcp/overview) | | **Proxy** | [ace-tool (GitHub)](https://github.com/eastxiaodong/ace-tool) |
--- ## πŸ“š CodexLens Local Search > ⚠️ **In Development**: CodexLens is under iterative optimization. Some features may be unstable.
Search ModeDescription
FTSFull-text search, based on SQLite FTS5
SemanticSemantic search, using local embedding models
HybridHybrid search, combining FTS + Semantic + Reranking
πŸ“¦ Installation ```bash # Enter codex-lens directory cd codex-lens # Install dependencies pip install -e . # Initialize index codexlens index /path/to/project ``` Open Dashboard via `ccw view`, manage indexes and execute searches in **CodexLens Manager**.
--- ## πŸ’» CCW CLI Commands ```bash ccw install # Install workflow files ccw view # Open dashboard ccw cli -p "..." # Execute CLI tools (Gemini/Qwen/Codex) ccw upgrade -a # Upgrade all installations ``` ### Dashboard Features
FeatureDescription
Session OverviewTrack workflow sessions and progress
CodexLensFTS + Semantic + Hybrid code search
Graph ExplorerInteractive code relationship visualization
CLI ManagerExecution history with session resume
--- ## πŸ“– Documentation
| Document | Description | |----------|-------------| | [**Workflow Guide**](WORKFLOW_GUIDE.md) | 4-level workflow system (recommended) | | [**Getting Started**](GETTING_STARTED.md) | 5-minute quick start | | [**Dashboard Guide**](DASHBOARD_GUIDE.md) | Dashboard user guide | | [**FAQ**](FAQ.md) | Common questions | | [**Changelog**](CHANGELOG.md) | Version history |
--- ## πŸ—οΈ Architecture ``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Main Workflow (4 Levels) β”‚ β”‚ ⚑ Level 1: lite-lite-lite (instant, no artifacts) β”‚ β”‚ πŸ“ Level 2: lite-plan / lite-fix / multi-cli-plan (β†’ execute) β”‚ β”‚ πŸ“Š Level 3: plan / tdd-plan / test-fix-gen (session persist) β”‚ β”‚ 🧠 Level 4: brainstorm:auto-parallel β†’ plan β†’ execute β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ↓ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Issue Workflow (Supplement) β”‚ β”‚ πŸ” discover β†’ πŸ“‹ plan β†’ πŸ“¦ queue β†’ ▢️ execute (worktree) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` **Core Principles:** - ⚑ **Dependency Analysis** solves parallelism - no worktree needed for main workflow - πŸ”§ **Issue Workflow** supplements main workflow for post-development maintenance - 🎯 Select workflow level based on complexity - avoid over-engineering --- ## 🀝 Contributing
GitHub Issues Contributing
--- ## πŸ“„ License
MIT License - see [LICENSE](LICENSE)