BREAKING CHANGE: Remove CONFLICT_RESOLUTION.md generation in favor of interactive user confirmation and direct file modifications Core Changes: - Replace markdown report generation with structured JSON output for programmatic processing - Add interactive conflict resolution via AskUserQuestion (max 4 conflicts, 2-4 strategies each) - Apply modifications directly to guidance-specification.md and role analyses (*.md) using Edit tool - Update context-package.json with conflict_risk status (resolved/none/low) - Remove Phase 3 output validation (no file generation needed) Modified Files: - conflict-resolution.md: Complete rewrite of agent prompt and execution flow - Step 4: JSON output instead of markdown generation - Phase 3: User confirmation via AskUserQuestion - Phase 4: Apply modifications using Edit tool - Success criteria updated for in-place modifications - plan.md: Update Phase 3 data flow and TodoWrite pattern - Data flow now shows "Apply modifications via Edit tool" - Todo description changed to "Resolve conflicts and apply fixes" - task-generate-agent.md: Update conflict resolution context description - No longer references CONFLICT_RESOLUTION.md file - Notes conflicts resolved in guidance-specification.md and role analyses - task-generate.md: Comprehensive cleanup of all CONFLICT_RESOLUTION.md references - Remove CONFLICT_RESOLUTION.md from artifact catalog - Update load_planning_context step to read guidance-specification.md - Update task implementation logic_flow - Update artifact priority and integration sections - Update directory structure documentation Benefits: - Seamless workflow: conflicts detected → user confirms → applied automatically - No intermediate files to manage - User interaction at decision point (not after-the-fact) - Resolved conflicts integrated directly into source artifacts - Clear conflict_risk status tracking in context-package.json 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
🚀 Claude Code Workflow (CCW)
Claude Code Workflow (CCW) transforms AI development from simple prompt chaining into a robust, context-first orchestration system. It solves execution uncertainty and error accumulation through structured planning, deterministic execution, and intelligent multi-model orchestration.
🎉 Version 5.0: Less is More
Core Improvements:
- ✅ Removed External Dependencies - Using standard ripgrep/find instead of MCP code-index for better stability
- ✅ Streamlined Workflows - Enhanced TDD workflow with conflict resolution mechanism
- ✅ Focused on Role Analysis - Simplified planning architecture centered on role documents
See CHANGELOG.md for full details.
📚 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 differentiate it from traditional AI development approaches:
- Context-First Architecture: Pre-defined context gathering eliminates execution uncertainty by ensuring agents have the correct information before implementation.
- JSON-First State Management: Task states live in
.task/IMPL-*.jsonfiles as the single source of truth, enabling programmatic orchestration without state drift. - Autonomous Multi-Phase Orchestration: Commands chain specialized sub-commands and agents to automate complex workflows with zero user intervention.
- Multi-Model Strategy: Leverages the unique strengths of different AI models (Gemini for analysis, Codex for implementation) for superior results.
- Hierarchical Memory System: A 4-layer documentation system provides context at the appropriate level of abstraction, preventing information overload.
- Specialized Role-Based Agents: A suite of agents (
@code-developer,@test-fix-agent, etc.) mirrors a real software team to handle diverse tasks.
⚙️ Installation
For detailed installation instructions, please refer to the INSTALL.md guide.
🚀 Quick One-Line Installation
Windows (PowerShell):
Invoke-Expression (Invoke-WebRequest -Uri "https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.ps1" -UseBasicParsing).Content
Linux/macOS (Bash/Zsh):
bash <(curl -fsSL https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.sh)
✅ Verify Installation
After installation, open Claude Code and check if the workflow commands are available by running:
/workflow:session:list
If the slash commands (e.g., /workflow:*) are recognized, the installation was successful.
🛠️ Command Reference
CCW provides a rich set of commands for managing workflows, tasks, and interacting with AI tools. For a complete list and detailed descriptions of all available commands, please see the COMMAND_REFERENCE.md file.
For a detailed technical specification of every command, see the COMMAND_SPEC.md.
🚀 Getting Started
The best way to get started is to follow the 5-minute tutorial in the Getting Started Guide.
Here is a quick example of a common development workflow:
- Create a Plan (automatically starts a session):
/workflow:plan "Implement JWT-based user login and registration" - Execute the Plan:
/workflow:execute - Check Status (optional):
/workflow:status
🤝 Contributing & Support
- Repository: GitHub - Claude-Code-Workflow
- Issues: Report bugs or request features on GitHub Issues.
- Discussions: Join the Community Forum.
📄 License
This project is licensed under the MIT License. See the LICENSE file for details.