Claude Code Workflow (CCW) transforms AI development from simple prompt chaining into a powerful, context-first orchestration system. It solves execution uncertainty and error accumulation through structured planning, deterministic execution, and intelligent multi-model orchestration.
π Version 5.9.2: Lite-Fix Workflow Enhancement & Session Management
Core Improvements:
- β¨ Lite-Fix Session Artifacts (
/workflow:lite-fix) - Complete bug fix workflow tracking
- Session Folder Structure: Organized artifact storage in
.workflow/.lite-fix/{bug-slug}-{timestamp}/- Phase Artifacts:
diagnosis.json,impact.json,fix-plan.json,task.json- CLI/Agent Access: All intermediate results accessible for execution tools
- Follow-up Tasks: Auto-generated comprehensive fix and postmortem tasks (hotfix mode)
- Enhanced Task JSON: Complete context package with diagnosis, impact, and fix plan
- π Consistent Architecture - Aligned with lite-plan session management patterns
- π Better Audit Trail - Natural history tracking for all bug fixes
- π― Improved Reusability - Task JSON files can be re-executed with
/workflow:lite-executeSee CHANGELOG.md for complete details.
π New to CCW? Check out the Getting Started Guide for a beginner-friendly 5-minute tutorial!
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.
For detailed installation instructions, refer to the INSTALL.md guide.
Windows (PowerShell):
Invoke-Expression (Invoke-WebRequest -Uri "https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.ps1" -UseBasicParsing).ContentLinux/macOS (Bash/Zsh):
bash <(curl -fsSL https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.sh)After installation, open Claude Code and verify that workflow commands are available by running:
/workflow:session:listIf slash commands (e.g., /workflow:*) are recognized, the installation was successful.
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.
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
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:
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
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)
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
CCW provides comprehensive documentation to help you get started quickly and master advanced features:
- 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
- Architecture Overview - System design and core components
- Project Introduction - Detailed project overview
- Workflow Diagrams - Visual workflow representations
- Command Reference - Complete list of all commands
- Command Spec - Detailed technical specifications
- Command Flow Standard - Command design patterns
- Contributing Guide - How to contribute to CCW
- Changelog - Version history and release notes
- 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.
This project is licensed under the MIT License. See the LICENSE file for details.