Files
Claude-Code-Workflow/.claude/workflows/unified-workflow-system-principles.md
catlog22 445ac823ba Initial release: Claude Code Workflow (CCW) v2.0
🚀 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>
2025-09-07 17:39:54 +08:00

98 lines
4.6 KiB
Markdown

# Workflow System Architecture
## Overview
**Foundation**: @./core-principles.md
This document defines the technical system architecture, component relationships, and coordination mechanisms that implement the core workflow principles.
## System Components
### Session Management
**Multi-Session Architecture**: Supports concurrent sessions with single active session pattern
**Registry System**: Global registry tracks all sessions, commands inherit active session context
**State Management**: Individual session state with phase-aware progress tracking
**Technical Details**: @./session-management-principles.md
### File Structure System
**Progressive Structure**: Scales from minimal structure for simple tasks to comprehensive organization for complex workflows
**Complexity Levels**: Three levels (0-2) with automatic structure generation based on task count and scope
**Standard Templates**: Consistent directory layouts and file naming across all complexity levels
**Technical Details**: @./file-structure-standards.md
### Chat and Summary Management
**Interaction Documentation**: Gemini CLI sessions automatically saved and cross-referenced with planning documents
**Task Summaries**: Comprehensive documentation of completed work with cross-referencing to implementation plans
**Integration**: Chat insights inform planning, summaries provide audit trail
**Technical Details**: @./file-structure-standards.md
### Task Management System
**Hierarchical Task Schema**: JSON-based task definitions with up to 3 levels of decomposition
**State Coordination**: Bidirectional sync between JSON task files, TODO_LIST.md, and workflow session
**Agent Integration**: Agent assignment based on task type with context preparation
**Progress Tracking**: Real-time progress calculation with dependency management
**Technical Details**: @./task-management-principles.md
### Document Generation Rules
**Complexity-Based Generation**: Automatic document creation based on task count, scope, and complexity
**Progressive Templates**: Standard document templates that scale with workflow complexity
**Auto-trigger Logic**: Conditional document generation based on predefined thresholds
**Technical Details**: @./task-decomposition-integration.md
### Brainstorming Integration
**Context Preservation**: Multi-role brainstorming analysis automatically integrated into planning documents
**Cross-Referencing**: Task context includes references to relevant brainstorming insights
**Synthesis Integration**: Planning documents synthesize brainstorming outputs into actionable strategies
**Technical Details**: @./file-structure-standards.md
## Coordination System
### Data Ownership and Synchronization
**Clear Ownership**: Each document type owns specific data with defined synchronization rules
**Bidirectional Sync**: Automatic synchronization between JSON task files, TODO_LIST.md, and planning documents
**Conflict Resolution**: Prioritized resolution system based on ownership, timestamps, and consistency
**Technical Details**: @./task-management-principles.md
## Command Integration
### Embedded Workflow Logic
**Workflow Commands**: Session management, planning, and implementation with embedded document generation
**Task Commands**: Task creation, breakdown, execution, and status with automatic synchronization
**Manual Tools**: Maintenance operations for edge cases and manual intervention
**Technical Details**: See individual command documentation
## Implementation Flow
**Workflow Phases**: Session initialization → [Optional brainstorming] → Planning → Implementation → Review
**Progressive Complexity**: Structure and documentation automatically scale with task complexity
**Cross-Integration**: Real-time synchronization across all system components
## Quality Control
**Auto-Validation**: Task ID consistency, document references, progress calculations, cross-file integrity
**Error Recovery**: Automatic recovery strategies with manual fallback for complex conflicts
**Data Integrity**: Comprehensive validation and consistency checks across all workflow components
## Architecture Integration
This document provides the technical architecture framework. For complete system documentation, see:
**📋 Complete Documentation**: @./workflow-overview.md
For specialized implementation details:
- **Session Management**: @./session-management-principles.md
- **Task System**: @./task-management-principles.md
- **Complexity Rules**: @./task-decomposition-integration.md
- **File Structure**: @./file-structure-standards.md
- **TodoWrite Integration**: @./todowrite-coordination-rules.md
---
**Architecture ensures**: Technical framework supporting core principles with scalable component coordination