mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-05 01:50:27 +08:00
09d99abee6
* feat(security): Secure dashboard server by default ## Solution Summary - Solution-ID: SOL-DSC-002-1 - Issue-ID: DSC-002 ## Tasks Completed - [T1] JWT token manager (24h expiry, persisted secret/token) - [T2] API auth middleware + localhost token endpoint - [T3] Default bind 127.0.0.1, add --host with warning - [T4] Localhost-only CORS with credentials + Vary - [T5] SECURITY.md documentation + README link ## Verification - npm run build - npm test -- ccw/tests/token-manager.test.ts ccw/tests/middleware.test.ts ccw/tests/server-auth.integration.test.ts ccw/tests/server.test.ts ccw/tests/cors.test.ts * fix(security): Prevent command injection in Windows spawn() ## Solution Summary - **Solution-ID**: SOL-DSC-001-1 - **Issue-ID**: DSC-001 - **Risk/Impact/Complexity**: high/high/medium ## Tasks Completed - [T1] Create Windows shell escape utility - [T2] Escape cli-executor spawn() args on Windows - [T3] Add command injection regression tests ## Files Modified - ccw/src/utils/shell-escape.ts - ccw/src/tools/cli-executor.ts - ccw/tests/shell-escape.test.ts - ccw/tests/security/command-injection.test.ts ## Verification - npm run build - npm test -- ccw/tests/shell-escape.test.ts ccw/tests/security/command-injection.test.ts * fix(security): Harden path validation (DSC-005) ## Solution Summary - Solution-ID: SOL-DSC-005-1 - Issue-ID: DSC-005 ## Tasks Completed - T1: Refactor path validation to pre-resolution checking - T2: Implement allowlist-based path validation - T3: Add path validation to API routes - T4: Add path security regression tests ## Files Modified - ccw/src/utils/path-resolver.ts - ccw/src/utils/path-validator.ts - ccw/src/core/routes/graph-routes.ts - ccw/src/core/routes/files-routes.ts - ccw/src/core/routes/skills-routes.ts - ccw/tests/path-resolver.test.ts - ccw/tests/graph-routes.test.ts - ccw/tests/files-routes.test.ts - ccw/tests/skills-routes.test.ts - ccw/tests/security/path-traversal.test.ts ## Verification - npm run build - npm test -- path-resolver.test.ts - npm test -- path-validator.test.ts - npm test -- graph-routes.test.ts - npm test -- files-routes.test.ts - npm test -- skills-routes.test.ts - npm test -- ccw/tests/security/path-traversal.test.ts * fix(security): Prevent credential leakage (DSC-004) ## Solution Summary - Solution-ID: SOL-DSC-004-1 - Issue-ID: DSC-004 ## Tasks Completed - T1: Create credential handling security tests - T2: Add log sanitization tests - T3: Add env var leakage prevention tests - T4: Add secure storage tests ## Files Modified - ccw/src/config/litellm-api-config-manager.ts - ccw/src/core/routes/litellm-api-routes.ts - ccw/tests/security/credential-handling.test.ts ## Verification - npm run build - node --experimental-strip-types --test ccw/tests/security/credential-handling.test.ts * test(ranking): expand normalize_weights edge case coverage (ISS-1766920108814-0) ## Solution Summary - Solution-ID: SOL-20251228113607 - Issue-ID: ISS-1766920108814-0 ## Tasks Completed - T1: Fix NaN and invalid total handling in normalize_weights - T2: Add unit tests for NaN edge cases in normalize_weights ## Files Modified - codex-lens/tests/test_rrf_fusion.py ## Verification - python -m pytest codex-lens/tests/test_rrf_fusion.py::TestNormalizeBM25Score -v - python -m pytest codex-lens/tests/test_rrf_fusion.py -v -k normalize - python -m pytest codex-lens/tests/test_rrf_fusion.py::TestReciprocalRankFusion::test_weight_normalization codex-lens/tests/test_cli_hybrid_search.py::TestCLIHybridSearch::test_weights_normalization -v * feat(security): Add CSRF protection and tighten CORS (DSC-006) ## Solution Summary - Solution-ID: SOL-DSC-006-1 - Issue-ID: DSC-006 - Risk/Impact/Complexity: high/high/medium ## Tasks Completed - T1: Create CSRF token generation system - T2: Add CSRF token endpoints - T3: Implement CSRF validation middleware - T4: Restrict CORS to trusted origins - T5: Add CSRF security tests ## Files Modified - ccw/src/core/auth/csrf-manager.ts - ccw/src/core/auth/csrf-middleware.ts - ccw/src/core/routes/auth-routes.ts - ccw/src/core/server.ts - ccw/tests/csrf-manager.test.ts - ccw/tests/auth-routes.test.ts - ccw/tests/csrf-middleware.test.ts - ccw/tests/security/csrf.test.ts ## Verification - npm run build - node --experimental-strip-types --test ccw/tests/csrf-manager.test.ts - node --experimental-strip-types --test ccw/tests/auth-routes.test.ts - node --experimental-strip-types --test ccw/tests/csrf-middleware.test.ts - node --experimental-strip-types --test ccw/tests/cors.test.ts - node --experimental-strip-types --test ccw/tests/security/csrf.test.ts * fix(cli-executor): prevent stale SIGKILL timeouts ## Solution Summary - Solution-ID: SOL-DSC-007-1 - Issue-ID: DSC-007 - Risk/Impact/Complexity: low/low/low ## Tasks Completed - [T1] Store timeout handle in killCurrentCliProcess ## Files Modified - ccw/src/tools/cli-executor.ts - ccw/tests/cli-executor-kill.test.ts ## Verification - node --experimental-strip-types --test ccw/tests/cli-executor-kill.test.ts * fix(cli-executor): enhance merge validation guards ## Solution Summary - Solution-ID: SOL-DSC-008-1 - Issue-ID: DSC-008 - Risk/Impact/Complexity: low/low/low ## Tasks Completed - [T1] Enhance sourceConversations array validation ## Files Modified - ccw/src/tools/cli-executor.ts - ccw/tests/cli-executor-merge-validation.test.ts ## Verification - node --experimental-strip-types --test ccw/tests/cli-executor-merge-validation.test.ts * refactor(core): remove @ts-nocheck from core routes ## Solution Summary - Solution-ID: SOL-DSC-003-1 - Issue-ID: DSC-003 - Queue-ID: QUE-20260106-164500 - Item-ID: S-9 ## Tasks Completed - T1: Create shared RouteContext type definition - T2: Remove @ts-nocheck from small route files - T3: Remove @ts-nocheck from medium route files - T4: Remove @ts-nocheck from large route files - T5: Remove @ts-nocheck from remaining core files ## Files Modified - ccw/src/core/dashboard-generator-patch.ts - ccw/src/core/dashboard-generator.ts - ccw/src/core/routes/ccw-routes.ts - ccw/src/core/routes/claude-routes.ts - ccw/src/core/routes/cli-routes.ts - ccw/src/core/routes/codexlens-routes.ts - ccw/src/core/routes/discovery-routes.ts - ccw/src/core/routes/files-routes.ts - ccw/src/core/routes/graph-routes.ts - ccw/src/core/routes/help-routes.ts - ccw/src/core/routes/hooks-routes.ts - ccw/src/core/routes/issue-routes.ts - ccw/src/core/routes/litellm-api-routes.ts - ccw/src/core/routes/litellm-routes.ts - ccw/src/core/routes/mcp-routes.ts - ccw/src/core/routes/mcp-routes.ts.backup - ccw/src/core/routes/mcp-templates-db.ts - ccw/src/core/routes/nav-status-routes.ts - ccw/src/core/routes/rules-routes.ts - ccw/src/core/routes/session-routes.ts - ccw/src/core/routes/skills-routes.ts - ccw/src/core/routes/status-routes.ts - ccw/src/core/routes/system-routes.ts - ccw/src/core/routes/types.ts - ccw/src/core/server.ts - ccw/src/core/websocket.ts ## Verification - npm run build - npm test * refactor: split cli-executor and codexlens routes into modules ## Solution Summary - Solution-ID: SOL-DSC-012-1 - Issue-ID: DSC-012 - Risk/Impact/Complexity: medium/medium/high ## Tasks Completed - [T1] Extract execution orchestration from cli-executor.ts (Refactor ccw/src/tools) - [T2] Extract route handlers from codexlens-routes.ts (Refactor ccw/src/core/routes) - [T3] Extract prompt concatenation logic from cli-executor (Refactor ccw/src/tools) - [T4] Document refactored module architecture (Docs) ## Files Modified - ccw/src/tools/cli-executor.ts - ccw/src/tools/cli-executor-core.ts - ccw/src/tools/cli-executor-utils.ts - ccw/src/tools/cli-executor-state.ts - ccw/src/tools/cli-prompt-builder.ts - ccw/src/tools/README.md - ccw/src/core/routes/codexlens-routes.ts - ccw/src/core/routes/codexlens/config-handlers.ts - ccw/src/core/routes/codexlens/index-handlers.ts - ccw/src/core/routes/codexlens/semantic-handlers.ts - ccw/src/core/routes/codexlens/watcher-handlers.ts - ccw/src/core/routes/codexlens/utils.ts - ccw/src/core/routes/codexlens/README.md ## Verification - npm run build - npm test * test(issue): Add comprehensive issue command tests ## Solution Summary - **Solution-ID**: SOL-DSC-009-1 - **Issue-ID**: DSC-009 - **Risk/Impact/Complexity**: low/high/medium ## Tasks Completed - [T1] Create issue command test file structure: Create isolated test harness - [T2] Add JSONL read/write operation tests: Verify JSONL correctness and errors - [T3] Add issue lifecycle tests: Verify status transitions and timestamps - [T4] Add solution binding tests: Verify binding flows and error cases - [T5] Add queue formation tests: Verify queue creation, IDs, and DAG behavior - [T6] Add queue execution tests: Verify next/done/retry and status sync ## Files Modified - ccw/src/commands/issue.ts - ccw/tests/issue-command.test.ts ## Verification - node --experimental-strip-types --test ccw/tests/issue-command.test.ts * test(routes): Add integration tests for route modules ## Solution Summary - Solution-ID: SOL-DSC-010-1 - Issue-ID: DSC-010 - Queue-ID: QUE-20260106-164500 ## Tasks Completed - [T1] Add tests for ccw-routes.ts - [T2] Add tests for files-routes.ts - [T3] Add tests for claude-routes.ts (includes Windows path fix for create) - [T4] Add tests for issue-routes.ts - [T5] Add tests for help-routes.ts (avoid hanging watchers) - [T6] Add tests for nav-status-routes.ts - [T7] Add tests for hooks/graph/rules/skills/litellm-api routes ## Files Modified - ccw/src/core/routes/claude-routes.ts - ccw/src/core/routes/help-routes.ts - ccw/tests/integration/ccw-routes.test.ts - ccw/tests/integration/claude-routes.test.ts - ccw/tests/integration/files-routes.test.ts - ccw/tests/integration/issue-routes.test.ts - ccw/tests/integration/help-routes.test.ts - ccw/tests/integration/nav-status-routes.test.ts - ccw/tests/integration/hooks-routes.test.ts - ccw/tests/integration/graph-routes.test.ts - ccw/tests/integration/rules-routes.test.ts - ccw/tests/integration/skills-routes.test.ts - ccw/tests/integration/litellm-api-routes.test.ts ## Verification - node --experimental-strip-types --test ccw/tests/integration/ccw-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/files-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/claude-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/issue-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/help-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/nav-status-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/hooks-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/graph-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/rules-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/skills-routes.test.ts - node --experimental-strip-types --test ccw/tests/integration/litellm-api-routes.test.ts * refactor(core): Switch cache and lite scanning to async fs ## Solution Summary - Solution-ID: SOL-DSC-013-1 - Issue-ID: DSC-013 - Queue-ID: QUE-20260106-164500 ## Tasks Completed - [T1] Convert cache-manager.ts to async file operations - [T2] Convert lite-scanner.ts to async file operations - [T3] Update cache-manager call sites to await async API - [T4] Update lite-scanner call sites to await async API ## Files Modified - ccw/src/core/cache-manager.ts - ccw/src/core/lite-scanner.ts - ccw/src/core/data-aggregator.ts ## Verification - npm run build - npm test * fix(exec): Add timeout protection for execSync ## Solution Summary - Solution-ID: SOL-DSC-014-1 - Issue-ID: DSC-014 - Queue-ID: QUE-20260106-164500 ## Tasks Completed - [T1] Add timeout to execSync calls in python-utils.ts - [T2] Add timeout to execSync calls in detect-changed-modules.ts - [T3] Add timeout to execSync calls in claude-freshness.ts - [T4] Add timeout to execSync calls in issue.ts - [T5] Consolidate execSync timeout constants and audit coverage ## Files Modified - ccw/src/utils/exec-constants.ts - ccw/src/utils/python-utils.ts - ccw/src/tools/detect-changed-modules.ts - ccw/src/core/claude-freshness.ts - ccw/src/commands/issue.ts - ccw/src/tools/smart-search.ts - ccw/src/tools/codex-lens.ts - ccw/src/core/routes/codexlens/config-handlers.ts ## Verification - npm run build - npm test - node --experimental-strip-types --test ccw/tests/issue-command.test.ts * feat(cli): Add progress spinner with elapsed time for long-running operations ## Solution Summary - Solution-ID: SOL-DSC-015-1 - Issue-ID: DSC-015 - Queue-Item: S-15 - Risk/Impact/Complexity: low/medium/low ## Tasks Completed - [T1] Add progress spinner to CLI execution: Update ccw/src/commands/cli.ts ## Files Modified - ccw/src/commands/cli.ts - ccw/tests/cli-command.test.ts ## Verification - node --experimental-strip-types --test ccw/tests/cli-command.test.ts - node --experimental-strip-types --test ccw/tests/cli-executor-kill.test.ts - node --experimental-strip-types --test ccw/tests/cli-executor-merge-validation.test.ts * fix(cli): Move full output hint immediately after truncation notice ## Solution Summary - Solution-ID: SOL-DSC-016-1 - Issue-ID: DSC-016 - Queue-Item: S-16 - Risk/Impact/Complexity: low/high/low ## Tasks Completed - [T1] Relocate output hint after truncation: Update ccw/src/commands/cli.ts ## Files Modified - ccw/src/commands/cli.ts - ccw/tests/cli-command.test.ts ## Verification - npm run build - node --experimental-strip-types --test ccw/tests/cli-command.test.ts * feat(cli): Add confirmation prompts for destructive operations ## Solution Summary - Solution-ID: SOL-DSC-017-1 - Issue-ID: DSC-017 - Queue-Item: S-17 - Risk/Impact/Complexity: low/high/low ## Tasks Completed - [T1] Add confirmation to storage clean operations: Update ccw/src/commands/cli.ts - [T2] Add confirmation to issue queue delete: Update ccw/src/commands/issue.ts ## Files Modified - ccw/src/commands/cli.ts - ccw/src/commands/issue.ts - ccw/tests/cli-command.test.ts - ccw/tests/issue-command.test.ts ## Verification - npm run build - node --experimental-strip-types --test ccw/tests/cli-command.test.ts - node --experimental-strip-types --test ccw/tests/issue-command.test.ts * feat(cli): Improve multi-line prompt guidance ## Solution Summary - Solution-ID: SOL-DSC-018-1 - Issue-ID: DSC-018 - Queue-Item: S-18 - Risk/Impact/Complexity: low/medium/low ## Tasks Completed - [T1] Update CLI help to emphasize --file option: Update ccw/src/commands/cli.ts - [T2] Add inline hint for multi-line detection: Update ccw/src/commands/cli.ts ## Files Modified - ccw/src/commands/cli.ts - ccw/tests/cli-command.test.ts ## Verification - npm run build - node --experimental-strip-types --test ccw/tests/cli-command.test.ts --------- Co-authored-by: catlog22 <catlog22@github.com>
🚀 Claude Code Workflow (CCW)
Claude Code Workflow (CCW) is a JSON-driven multi-agent development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. It transforms AI development from simple prompt chaining into a powerful orchestration system.
🎉 Version 6.3.18: Native CodexLens & Dashboard Revolution
Breaking Changes:
- ⚠️ CLI command refactored:
ccw cli exec→ccw cli -p- ⚠️ Code Index MCP replaced with native CodexLens
- ⚠️ Knowledge Graph replaced with Session Clustering
Core Features:
- 🔍 Native CodexLens: Full-Text Search + Semantic Search + HNSW vector index
- 🖥️ New Dashboard Views: CLAUDE.md Manager, Skills Manager, Graph Explorer, Core Memory
- 📘 TypeScript Migration: Full backend modernization
- 🧠 Session Clustering: Intelligent memory management with cluster visualization
See CHANGELOG.md for complete details and migration guide.
📚 New to CCW? Check out the Getting Started Guide for a beginner-friendly 5-minute tutorial!
✨ Core Concepts
CCW is built on a set of core principles that distinguish it from traditional AI development approaches:
- Context-First Architecture: Eliminates uncertainty during execution through pre-defined context gathering, ensuring agents have the right information before implementation.
- JSON-First State Management: Task state is fully stored in
.task/IMPL-*.jsonfiles as the single source of truth, enabling programmatic orchestration without state drift. - Autonomous Multi-Stage Orchestration: Commands chain-invoke specialized sub-commands and agents to automate complex workflows with zero user intervention.
- Multi-Model Strategy: Leverages the unique strengths of different AI models (e.g., Gemini for analysis, Codex for implementation) for superior results.
- Layered Memory System: A 4-tier documentation system that provides context at the appropriate abstraction level, preventing information overload.
- Specialized Role-Based Agents: A suite of agents (
@code-developer,@test-fix-agent, etc.) that emulate a real software team for diverse tasks.
⚙️ Installation
📋 Requirements
| Platform | Node.js | Additional |
|---|---|---|
| Windows | 20.x or 22.x LTS (recommended) | Node 23+ requires Visual Studio Build Tools |
| macOS | 18.x+ | Xcode Command Line Tools |
| Linux | 18.x+ | build-essential |
Note
: The
better-sqlite3dependency requires native compilation. Using Node.js LTS versions avoids build issues.
📦 npm Install (Recommended)
Install globally via npm:
npm install -g claude-code-workflow
Then install workflow files to your system:
# Interactive installation
ccw install
# Global installation (to ~/.claude)
ccw install -m Global
# Project-specific installation
ccw install -m Path -p /path/to/project
✅ Verify Installation
After installation, open Claude Code and verify that workflow commands are available by running:
/workflow:session:list
If slash commands (e.g., /workflow:*) are recognized, the installation was successful.
🖥️ CCW CLI Tool
The ccw command provides a powerful CLI for managing your Claude Code Workflow installation:
Commands
| Command | Description |
|---|---|
ccw install |
Install workflow files to Global (~/.claude) or specific Path |
ccw upgrade |
Upgrade existing installations to current package version |
ccw uninstall |
Remove workflow files from an installation |
ccw view |
Open the workflow dashboard in browser |
ccw serve |
Start dashboard server without opening browser |
ccw list |
List all managed installations |
ccw cli -p "..." |
Execute CLI tools (Gemini/Qwen/Codex) with prompt |
ccw core-memory |
Manage session clustering and memory |
Usage Examples
# Install globally
ccw install -m Global
# Install to specific project
ccw install -m Path -p ./my-project
# Open dashboard
ccw view
# Start dashboard server on custom port
ccw serve --port 8080
# Upgrade all installations
ccw upgrade -a
# List installations
ccw list
Dashboard Features
The CCW Dashboard (ccw view) provides:
- 📊 Session Overview: View all workflow sessions with status and progress
- 📋 Task Management: Track task execution and completion
- 🔍 CodexLens Manager: Native code indexing with FTS + Semantic + Hybrid search
- 🧠 Core Memory: Session clustering visualization with cluster management
- 📄 CLAUDE.md Manager: File tree viewer for configuration management
- 🎯 Skills Manager: View and manage Claude Code skills
- 🕸️ Graph Explorer: Interactive code relationship visualization (Cytoscape.js)
- ⚙️ MCP Manager: Configure and monitor MCP servers
- 🪝 Hook Manager: Manage Claude Code hooks
- ❓ Help View: Internationalized help documentation
- 💻 CLI Manager: CLI execution history with session resume
📖 See Dashboard Guide and Dashboard Operations for detailed documentation.
🔒 Security
The dashboard server is localhost-bound by default and API endpoints require authentication. See ccw/docs/SECURITY.md for the full security model, token usage, and safe deployment guidance.
🛠️ Command Reference
CCW provides a rich set of commands for managing workflows, tasks, and interactions with AI tools. For a complete list and detailed descriptions of all available commands, please refer to the COMMAND_REFERENCE.md file.
For detailed technical specifications of each command, see COMMAND_SPEC.md.
💡 Need Help? Use the Interactive Command Guide
CCW includes a built-in Command Guide Skill to help you discover and use commands effectively:
CCW-help- Get interactive help and command recommendationsCCW-issue- Report bugs or request features using guided templates
The Command Guide provides:
- 🔍 Smart Command Search - Find commands by keyword, category, or use case
- 🤖 Next-Step Recommendations - Get suggestions for what to do after any command
- 📖 Detailed Documentation - View arguments, examples, and best practices
- 🎓 Beginner Onboarding - Learn the 14 core commands through guided learning paths
- 📝 Issue Reporting - Generate standardized bug reports and feature requests
Usage Examples:
User: "CCW-help"
→ Interactive menu with command search, recommendations, and documentation
User: "What should I do after /workflow:plan?"
→ Recommends /workflow:execute, /workflow:action-plan-verify with workflow patterns
User: "CCW-issue"
→ Guided template generation for bugs, features, or question inquiries
🚀 Quick Start
The best way to get started is by following the 5-minute tutorial in the Getting Started Guide.
Here's a quick example of a common development workflow:
Option 1: Lite-Plan Workflow (⚡ Recommended for Quick Tasks)
Lightweight interactive workflow with in-memory planning and immediate execution:
# Basic usage with auto-detection
/workflow:lite-plan "Add JWT authentication to user login"
# Force code exploration
/workflow:lite-plan -e "Refactor logging module for better performance"
# Basic usage
/workflow:lite-plan "Add unit tests for authentication service"
Interactive Flow:
- Phase 1: Automatic task analysis and smart code exploration (if needed)
- Phase 2: Answer clarification questions (if any)
- Phase 3: Review generated plan and task breakdown
- Phase 4: Three-dimensional confirmation:
- ✅ Confirm/Modify/Cancel task
- 🔧 Choose execution: Agent / Provide Plan Only / CLI (Gemini/Qwen/Codex)
- 🔍 Optional code review: No / Claude / Gemini / Qwen / Codex
- Phase 5: Watch live execution and task tracking
Option 2: Lite-Fix Workflow (🐛 Recommended for Bug Fixes)
Intelligent bug diagnosis and fix workflow with adaptive severity assessment:
# Standard bug fix (auto-adapts based on severity)
/workflow:lite-fix "User avatar upload fails with 413 error"
# Production hotfix mode
/workflow:lite-fix --hotfix "Payment gateway 5xx errors"
Workflow Features:
- Phase 1: Intelligent root cause diagnosis with adaptive search
- Phase 2: Automatic impact assessment and risk scoring
- Phase 3: Fix strategy generation based on complexity
- Phase 4: Risk-aware verification planning
- Phase 5: User confirmation with execution selection
- Phase 6: Execution dispatch with complete artifact tracking
Session Artifacts (saved to .workflow/.lite-fix/{bug-slug}-{timestamp}/):
diagnosis.json- Root cause analysis and reproduction stepsimpact.json- Risk score, severity, and workflow adaptationsfix-plan.json- Fix strategy and implementation taskstask.json- Enhanced Task JSON with complete contextfollowup.json- Auto-generated follow-up tasks (hotfix mode only)
Option 3: Full Workflow (📋 Comprehensive Planning)
Traditional multi-stage workflow for complex projects:
- Create Plan (auto-starts session):
/workflow:plan "Implement JWT-based user login and registration" - Execute Plan:
/workflow:execute - View Status (optional):
/workflow:status
📚 Documentation
CCW provides comprehensive documentation to help you get started quickly and master advanced features:
📖 Getting Started
- Getting Started Guide - 5-minute quick start tutorial
- Installation Guide - Detailed installation instructions (中文)
- Workflow Decision Guide - 🌳 Interactive flowchart to choose the right command
- Examples - Real-world use cases and practical examples
- FAQ - Common questions and troubleshooting
🖥️ Dashboard
- Dashboard Guide - Dashboard user guide and interface overview
- Dashboard Operations - Detailed operation instructions
🏗️ Architecture & Design
- Architecture Overview - System design and core components
- Project Introduction - Detailed project overview
- Workflow Diagrams - Visual workflow representations
📋 Command Reference
- Command Reference - Complete list of all commands
- Command Spec - Detailed technical specifications
- Command Flow Standard - Command design patterns
🤝 Contributing
- Contributing Guide - How to contribute to CCW
- Changelog - Version history and release notes
🤝 Contributing & Support
- Repository: GitHub - Claude-Code-Workflow
- Issues: Report bugs or request features on GitHub Issues.
- Discussions: Join the Community Forum.
- Contributing: See CONTRIBUTING.md for contribution guidelines.
📄 License
This project is licensed under the MIT License. See the LICENSE file for details.