mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +08:00
445ac823ba
🚀 Revolutionary AI-powered development workflow orchestration system ## 🔥 Core Innovations - **Document-State Separation**: Markdown for planning, JSON for execution state - **Progressive Complexity Management**: Level 0-2 adaptive workflow depth - **5-Agent Orchestration**: Specialized AI agents with context preservation - **Session-First Architecture**: Auto-discovery and state inheritance ## 🏗️ Key Features - Intelligent workflow orchestration (Simple/Medium/Complex patterns) - Real-time document-state synchronization with conflict resolution - Hierarchical task management with 3-level JSON structure - Gemini CLI integration with 12+ specialized templates - Comprehensive file output generation for all workflow commands ## 📦 Installation Remote one-liner installation: ``` iex (iwr -useb https://raw.githubusercontent.com/catlog22/Claude-CCW/main/install-remote.ps1) ``` ## 🎯 System Architecture 4-layer intelligent development architecture: 1. Command Layer - Smart routing and version management 2. Agent Layer - 5 specialized development agents 3. Workflow Layer - Gemini templates and task orchestration 4. Memory Layer - Distributed documentation and auto-sync 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
59 lines
2.0 KiB
Markdown
59 lines
2.0 KiB
Markdown
# Workflow Complexity Decision Tree
|
|
|
|
## Task Classification
|
|
|
|
```
|
|
Task Type?
|
|
├── Single file/bug fix → Simple Workflow
|
|
├── Multi-file feature → Medium Workflow
|
|
├── System changes → Complex Workflow
|
|
└── Uncertain complexity → Start with Medium, escalate if needed
|
|
```
|
|
|
|
## Complexity Patterns
|
|
|
|
### Always Use Simple Workflow For:
|
|
- Bug fixes in single files
|
|
- Minor UI adjustments
|
|
- Text/message updates
|
|
- Simple validation additions
|
|
- Quick documentation fixes
|
|
|
|
### Always Use Medium Workflow For:
|
|
- New feature implementations
|
|
- Multi-component changes
|
|
- API endpoint additions
|
|
- Database schema updates
|
|
- Integration implementations
|
|
|
|
### Always Use Complex Workflow For:
|
|
- Architecture changes
|
|
- Security implementations
|
|
- Performance optimizations
|
|
- Migration projects
|
|
- System integrations
|
|
- Authentication/authorization systems
|
|
|
|
## Workflow Pattern Matrix
|
|
|
|
| Task Type | Recommended Workflow | Agent Sequence | Iteration Requirements |
|
|
|-----------|---------------------|----------------|----------------------|
|
|
| Bug Fix (Simple) | Simple | code-developer → review | Minimal |
|
|
| Bug Fix (Complex) | Medium | planning → developer → review | 1 round |
|
|
| New Feature (Small) | Simple | developer → review | Minimal |
|
|
| New Feature (Large) | Medium | planning → developer → review | 1-2 rounds |
|
|
| Architecture Changes | Complex | planning → developer → review → iterate | Multiple rounds |
|
|
| Security Implementation | Complex | planning → developer → review → validate | Mandatory multiple rounds |
|
|
| Performance Optimization | Complex | planning → developer → review → test | Performance validation |
|
|
| Prototype Development | Simple | developer → minimal review | Fast |
|
|
|
|
## Progressive Complexity Strategy
|
|
|
|
```bash
|
|
# Start simple and escalate as needed
|
|
/workflow simple "initial implementation"
|
|
# If complexity emerges during development:
|
|
/workflow medium "enhance with additional requirements"
|
|
# If system-wide impact discovered:
|
|
/workflow complex "complete system integration"
|
|
``` |