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>
2026-02-05 01:50:27 +08:00 · 2025-09-07 17:39:54 +08:00
commit 445ac823ba
87 changed files with 19076 additions and 0 deletions
--- a/.claude/commands/task/create.md
+++ b/.claude/commands/task/create.md
@@ -0,0 +1,303 @@
+---
+name: task-create
+description: Create implementation tasks with automatic context awareness
+usage: /task:create "<title>" [--type=<type>] [--priority=<level>]
+argument-hint: "task title" [optional: type and priority]
+examples:
+  - /task:create "Implement user authentication"
+  - /task:create "Build REST API endpoints" --type=feature
+  - /task:create "Fix login validation bug" --type=bugfix --priority=high
+---
+
+# Task Create Command (/task:create)
+
+## Overview
+Creates new implementation tasks during IMPLEMENT phase with automatic context awareness and ID generation.
+
+## Core Principles
+**System:** @~/.claude/workflows/core-principles.md  
+**Task Management:** @~/.claude/workflows/task-management-principles.md
+
+## Features
+
+### Automatic Behaviors
+- **ID Generation**: Auto-generates impl-N hierarchical format (impl-N.M.P max depth)
+- **Context Inheritance**: Inherits from workflow session and IMPL_PLAN.md
+- **JSON File Creation**: Generates task JSON in `.workflow/WFS-[topic-slug]/.task/`
+- **Document Integration**: Creates/updates TODO_LIST.md based on complexity triggers
+- **Status Setting**: Initial status = "pending"
+- **Workflow Sync**: Updates workflow-session.json task list automatically
+- **Agent Assignment**: Suggests agent based on task type
+- **Hierarchy Support**: Creates parent-child relationships up to 3 levels
+- **Progressive Structure**: Auto-triggers enhanced structure at complexity thresholds
+
+### Context Awareness
+- Detects current workflow phase (must be IMPLEMENT)
+- Reads existing tasks from `.task/` directory to avoid duplicates
+- Inherits requirements and scope from workflow-session.json
+- Suggests related tasks based on existing JSON task hierarchy
+- Analyzes complexity for structure level determination (Level 0-2)
+
+## Usage
+
+### Basic Creation
+```bash
+/task:create "Build authentication module"
+```
+
+Output:
+```
+✅ Task created: impl-1
+Title: Build authentication module
+Type: feature
+Status: pending
+Depth: 1 (main task)
+Context inherited from workflow
+```
+
+### With Options
+```bash
+/task:create "Fix security vulnerability" --type=bugfix --priority=critical
+```
+
+### Task Types
+- `feature` - New functionality (default)
+- `bugfix` - Bug fixes
+- `refactor` - Code improvements
+- `test` - Test implementation
+- `docs` - Documentation
+
+### Priority Levels
+- `low` - Can be deferred
+- `normal` - Standard priority (default)
+- `high` - Should be done soon
+- `critical` - Must be done immediately
+
+## Task Structure
+
+```json
+{
+  "id": "impl-1",
+  "parent_id": null,
+  "title": "Build authentication module",
+  "type": "feature",
+  "priority": "normal",
+  "status": "pending",
+  "depth": 1,
+  "agent": "code-developer",
+  "effort": "4h",
+  
+  "context": {
+    "inherited_from": "WFS-user-auth-system",
+    "requirements": ["JWT authentication", "OAuth2 support"],
+    "scope": ["src/auth/*", "tests/auth/*"],
+    "acceptance": ["Module handles JWT tokens", "OAuth2 flow implemented"]
+  },
+  
+  "dependencies": {
+    "upstream": [],
+    "downstream": [],
+    "parent_dependencies": []
+  },
+  
+  "subtasks": [],
+  
+  "execution": {
+    "attempts": 0,
+    "current_attempt": null,
+    "history": []
+  },
+  
+  "metadata": {
+    "created_at": "2025-09-05T10:30:00Z",
+    "started_at": null,
+    "completed_at": null,
+    "last_updated": "2025-09-05T10:30:00Z",
+    "version": "1.0"
+  }
+}
+```
+
+## Document Integration Features
+
+### JSON Task File Generation
+**File Location**: `.workflow/WFS-[topic-slug]/.task/impl-[N].json`
+**Hierarchical Naming**: Follows impl-N.M.P format for nested tasks
+**Schema Compliance**: All JSON files follow unified task schema from task-management-principles.md
+
+### Import from IMPL_PLAN.md
+```bash
+/task:create --from-plan
+```
+- Reads existing IMPL_PLAN.md implementation strategy
+- Creates JSON task files based on planned structure
+- Maintains hierarchical relationships in JSON format
+- Preserves acceptance criteria from plan in task context
+
+### Progressive Document Creation
+Based on complexity analysis triggers:
+
+#### Level 0 Structure (<5 tasks)
+- Creates individual JSON task files in `.task/`
+- No TODO_LIST.md generation (minimal overhead)
+- Updates workflow-session.json with task references
+
+#### Level 1 Structure (5-15 tasks)
+- Creates hierarchical JSON task files (impl-N.M format)
+- **Auto-generates TODO_LIST.md** when complexity threshold reached
+- Creates `.summaries/` directory structure
+- Enhanced cross-referencing between files
+
+#### Level 2 Structure (>15 tasks)
+- Creates complete hierarchical JSON files (impl-N.M.P format)
+- Always maintains TODO_LIST.md with progress tracking
+- Full `.summaries/` directory with detailed task documentation
+- Comprehensive cross-references and validation
+
+### Document Creation Triggers
+TODO_LIST.md auto-generation conditions:
+- **Task count > 5** OR **modules > 3** OR **estimated effort > 4h** OR **complex dependencies detected**
+- **Always** for workflows with >15 tasks (Level 2 structure)
+
+### Cross-Reference Management
+- All JSON files contain proper parent_id relationships
+- TODO_LIST.md links to individual JSON task files
+- workflow-session.json maintains task list with hierarchy depth
+- Automatic validation of cross-file references
+
+## Context Inheritance
+
+Tasks automatically inherit:
+1. **Requirements** - From workflow-session.json context and IMPL_PLAN.md
+2. **Scope** - File patterns from workflow and IMPL_PLAN.md strategy
+3. **Standards** - Quality standards from workflow session
+4. **Dependencies** - Related tasks from existing JSON task hierarchy in `.task/`
+5. **Parent Context** - When created as subtasks, inherit from parent JSON file
+6. **Session Context** - Global workflow context from active session
+
+## Smart Suggestions
+
+Based on title analysis:
+```bash
+/task:create "Write unit tests for auth module"
+
+Suggestions:
+- Related task: impl-1 (Build authentication module)
+- Suggested agent: test-agent
+- Estimated effort: 2h
+- Dependencies: [impl-1]
+- Suggested hierarchy: impl-1.3 (as subtask of impl-1)
+```
+
+## Validation Rules
+
+1. **Phase Check** - Must be in IMPLEMENT phase (from workflow-session.json)
+2. **Duplicate Check** - Title similarity detection across existing JSON files
+3. **Session Validation** - Active workflow session must exist in `.workflow/`
+4. **ID Uniqueness** - Auto-increment to avoid conflicts in `.task/` directory
+5. **Hierarchy Validation** - Parent-child relationships must be valid (max 3 levels)
+6. **File System Validation** - Proper directory structure and naming conventions
+7. **JSON Schema Validation** - All task files conform to unified schema
+
+## Error Handling
+
+```bash
+# Not in IMPLEMENT phase
+❌ Cannot create tasks in PLAN phase
+→ Use: /workflow implement
+
+# No workflow session
+❌ No active workflow found
+→ Use: /workflow init "project name"
+
+# Duplicate task
+⚠️ Similar task exists: impl-3
+→ Continue anyway? (y/n)
+
+# Maximum depth exceeded
+❌ Cannot create impl-1.2.3.1 (exceeds 3-level limit)
+→ Suggest: impl-1.2.4 or promote to impl-2?
+```
+
+## Batch Creation
+
+Create multiple tasks at once:
+```bash
+/task:create --batch
+> Enter tasks (empty line to finish):
+> Build login endpoint
+> Add session management
+> Write authentication tests
+>
+
+Created 3 tasks:
+- impl-1: Build login endpoint
+- impl-2: Add session management  
+- impl-3: Write authentication tests
+```
+
+## File Output Management
+
+### JSON Task Files
+**Output Location**: `.workflow/WFS-[topic-slug]/.task/impl-[id].json`
+**Schema**: Follows unified task JSON schema with hierarchical support
+**Contents**: Complete task definition including context, dependencies, and metadata
+
+### TODO_LIST.md Generation
+**Trigger Logic**: Auto-created based on complexity thresholds
+**Location**: `.workflow/WFS-[topic-slug]/TODO_LIST.md`
+**Format**: Hierarchical task display with checkboxes and progress tracking
+
+### Summary Directory Structure
+**Location**: `.workflow/WFS-[topic-slug]/.summaries/`
+**Purpose**: Ready for task completion summaries
+**Structure**: Created when Level 1+ complexity detected
+
+### Workflow Session Updates
+**File**: `.workflow/WFS-[topic-slug]/workflow-session.json`
+**Updates**: Task list, counters, progress calculations, hierarchy depth
+
+## Integration
+
+### Workflow Integration
+- Updates workflow-session.json with new task references
+- Increments task counter and updates complexity assessment
+- Updates IMPLEMENT phase progress and task hierarchy depth
+- Maintains bidirectional sync with TodoWrite tool
+
+### File System Coordination
+- Validates and creates required directory structure
+- Maintains cross-references between all generated files
+- Ensures proper naming conventions and hierarchy limits
+- Provides rollback capability for failed operations
+
+### Next Steps
+After creation, use:
+- `/task:breakdown` - Split into hierarchical subtasks with JSON files
+- `/task:execute` - Run the task with summary generation
+- `/task:context` - View task details and file references
+- `/task:sync` - Validate file consistency across system
+
+## Examples
+
+### Feature Development
+```bash
+/task:create "Implement shopping cart functionality" --type=feature
+```
+
+### Bug Fix
+```bash
+/task:create "Fix memory leak in data processor" --type=bugfix --priority=high
+```
+
+### Refactoring
+```bash
+/task:create "Refactor database connection pool" --type=refactor
+```
+
+## Related Commands
+
+- `/task:breakdown` - Break task into hierarchical subtasks
+- `/task:context` - View/modify task context
+- `/task:execute` - Execute task with agent
+- `/task:status` - View task status and hierarchy