JSPM

  • Created
  • Published
  • Downloads 820
  • Score
    100M100P100Q106261F
  • License MIT

JSON-driven multi-agent development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (claude-code-workflow) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme


    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 for the complete 4-level workflow system.


    πŸš€ Quick Start

    Install CCW

    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

    # 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
    # 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:

    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
    Proxy ace-tool (GitHub)

    ⚠️ 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
    # 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

    CommandDescriptionWhen to Use
    /ccw Auto workflow orchestrator - analyzes intent, selects workflow level, executes command chain in main process βœ… General tasks, auto workflow selection, quick development
    /ccw-coordinator Smart orchestrator - intelligently recommends command chains, allows manual adjustment, executes via external CLI with state persistence πŸ”§ Complex multi-step workflows, customizable chains, resumable sessions

    Quick Examples:

    # /ccw - Auto workflow selection (Main Process)
    /ccw "Add user authentication"              # Auto-selects workflow based on intent
    /ccw "Fix memory leak in WebSocket"         # Detects bugfix workflow
    /ccw "Implement with TDD"                   # Routes to TDD workflow
    
    # /ccw-coordinator - Manual chain orchestration (External CLI)
    /ccw-coordinator "Implement OAuth2 system"  # Analyzes β†’ Recommends chain β†’ User confirms β†’ Executes

    Key Differences:

    Aspect /ccw /ccw-coordinator
    Execution Main process (SlashCommand) External CLI (background tasks)
    Selection Auto intent-based Smart recommendation + optional adjustment
    State TodoWrite tracking Persistent state.json
    Use Case General tasks, quick dev Complex chains, resumable

    Other CLI Commands

    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 4-level workflow system (recommended)
    Getting Started 5-minute quick start
    Dashboard Guide Dashboard user guide
    FAQ Common questions
    Changelog 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