What problem does it solve?
Coordinating multiple AI CLI tools (Gemini, Codex, Qwen, Claude, OpenCode) for code analysis and implementation tasks requires consistent prompt structures, correct tool selection, and safe permission handling, which is error-prone when done manually.
Core Features & Use Cases
- Configuration-Driven Tool Selection: Reads
~/.claude/cli-tools.json to route tasks to enabled tools by capability tags, with primary/secondary model fallback chains.
- Unified 6-Field Prompt Template: Standardizes PURPOSE, TASK, MODE, CONTEXT, EXPECTED, and CONSTRAINTS fields for every CLI invocation.
- Permission-Gated Modes: Enforces analysis (read-only), write (file modification), and review (git-aware, Codex-only) modes with explicit authorization.
- Use Case: Run a security audit by invoking
ccw cli with the analysis-assess-security-risks rule template against the auth module, then resume the session in write mode to implement the recommended fixes.
Quick Start
Ask the AI to analyze the authentication module for security vulnerabilities using the ccw cli with the security assessment rule template in analysis mode.